There will be times when customers will be asked to patch their installation of WebGUI, often to install test fixes (fixes that are provided due to urgency) or to install binaries that enable more verbose logging for debugging purposes when troubleshooting a PMR. But there have been more than a couple of incidents whereby patches were installed, but the fix or debug logging doesn't take effect.
Here are a few tips to ensure trouble-free installation of patches (test fixes / debug binaries).
- If the patch contains JAR files, and they often do, these original JAR files need to be moved out of their original directories OR have their file extension renamed e.g. server.jar to server.somedate.bak. This is to prevent the original JARs from being used by WebGUI
- A README file is always included with a test fix, and will list all the files to be replaced. It is important to verify that these files are backed up by cross-referencing the files (and its path) with the ones provided in the README, and use the same list again post-patch installation to confirm that all files were correctly replaced by checking their timestamp
- If you suspect that the file(s) were corrupted during download, do a checksum or file size check with fresh ones obtained from IBM support engineers
- Sometimes there will be JARs with identical names but reside in different directories (version.jar is one example) so if the files are being manually copied over to the target directories, care must be taken to prevent these files from being copied to the wrong location. Test fixes will often be given in a zip file with the correct directory structure so it is best to just unzip it according to the instructions in the accompanying README file
- Patches are custom built for each WebGUI release, so always check the README which will state clearly the target version. Do not apply any test fixes that is meant for a different release. The exact version can be obtained by logging into WebGUI as tipadmin and examining the output from 'Troubleshooting and Support > System Information for Tivoli Netcool/OMNIbus Web GUI' (WebGUI 7.3 and above) or 'TIP -> Troubleshooting and Support -> Netcool/Webtop System Information' (Webtop 2.2)
If the 5 steps above are observed, not only will the likely of failure will be greatly reduced, but it will speed up investigation if for some reason patching still fails.