Server HotFixes
All HotFixes, whether for the server or client, are initially installed on the Integrity Lifecycle Manager server using the PatchServer utility. For server-side HotFixes, the PatchServer utility extracts the updates and installs them on the server. Information on installing server-side HotFixes is included with the readme file for each HotFix.
|
|
• The Integrity Lifecycle Manager server must be restarted after installing any HotFix.
• HotFixes are bound to the service pack release they are based on. HotFixes based on one service pack release cannot be applied to a different service pack release. For example, HotFixes based on SP1 cannot be applied to SP2.
• If you attempt to re-install the same HotFix on the server, an error message displays.
|
In a multi-server environment, all servers should be maintained at the same HotFix level. If a proxy is hosting projects locally in a multi-server environment, it is also important to maintain that proxy at the same HotFix level.
After HotFix installation, a marker file is placed in the following folder on the Integrity Lifecycle Manager server and indicates which HotFixes have been installed:
installdir/installinfo
An installinfo file is also generated on the proxy when a HotFix is installed directly on a proxy. The marker file is a text file (.txt) and the file name is based on the HotFix number. As is the case with service packs, HotFixes are placed in the following location on the server:
installdir/server/patches/releasenumber
where
releasenumber is
JJ.NN.LL. (For more information on HotFix numbering, see
“HotFix ID Numbers and Install Information”).
If a new service pack is installed, it automatically removes any HotFixes that were based on previous service packs. When the
Integrity Lifecycle Manager server is restarted, the log of installed HotFixes is also updated accordingly. For more information, see
“Service Pack and HotFix Logging”.
|
|
The PatchServer.log and the SPInstall.log are also updated whenever a HotFix is installed.
|
Related Links
