![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
This section contains new information for documentation units of IBM Tivoli Configuration Manager, Version 4.2.
The following new information applies to the User's Guide for Software Distribution.
Cloning software packages from the Tivoli desktop
When cloning software packages from one profile manager to another using the drag-and-drop function, the cloned software package might not work correctly.
To clone a software package from one profile manager to another, perform the following steps:
You can also move a software package from one profile manager to another, by performing one of the following procedures:
The following new information applies to the User's Guide for Software Distribution.
Note: If you build packages on the source host system with a specific code set, you cannot perform a delta installation using another source host system with a different code set.
The following new information applies to the User's Guide for Software Distribution.
Note: For UNIX source hosts, directory and file name checks are case-sensitive, so the base and the version packages must use the same case.
The following new information applies to the Reference Manual for Software Distribution.
To apply the delta installation, the base and the version packages must have the same nested structure. In addition, if the base and the version packages use the same file in the same directory, the packages must be in software package block (built) format, otherwise the whole file is distributed. The above operation is performed on the source host and generates a delta package that is sent to the target.
To apply the delta installation, the base and the version packages must have the same nested structure. In addition, if the base and the version packages use the same file in the same directory, the packages must be in software package block (built) format, otherwise the whole file is distributed. Byte-level differencing uses dependency checking to verify that the base package has been installed.
The following new information applies to the User's Guide for Deployment Services.
The software packages distributed using Software Distribution are tracked in the Inventory database by the endpoint label, while the software packages distributed using the Web Interface are tracked by the workstation hostname. This condition can lead to a misalignment of information in the Inventory database if you install an endpoint on the Web Interface client workstation and distribute software packages to this workstation using Software Distribution.
To avoid this problem, you should install the endpoint with the same name as the workstation hostname or, if the endpoint is already installed, change its name to match the workstation hostname.
Information concerning software packages installed on a Web Interface client is not consistent when an endpoint is installed on the same workstation.
The software packages distributed using Software Distribution are tracked in the Inventory database by the endpoint label, while the software packages distributed using the Web Interface are tracked by the workstation hostname. This condition can lead to a misalignment of information in the Inventory database if you install an endpoint on the Web Interface client workstation and distribute software packages to this workstation using Software Distribution.
To avoid this problem, you should install the endpoint with the same name as the workstation hostname or, if the endpoint is already installed, change its name to match the workstation hostname.
The following new information applies to the Release Notes.
APAR IY64238: Repeated attempts to install the IBM Tivoli Configuration Manager Web Gateway on Windows 2000 Advanced Server dual processor workstations might cause the installation process to stop abruptly.
Workaround: Install the IBM Tivoli Configuration Manager Web Gateway component using an alternate installation method, such as the software package block or silent installation methods. For more information on these methods, refer to the IBM Tivoli Configuration Manager Planning and Installation Guide.
[ Top of Page | Previous Page | Next Page | Contents ]