A cumulative patch for IBM UrbanCode Build is typically a ZIP file, for example: ibm-ucb-220.127.116.11-cumulative-825828_2016-09-15.zip. The patch name includes the release the fix applies to and the date of the fix. The example patch is for version 18.104.22.168 and created on September 9, 2016. It can be applied to any IBM UrbanCode Build 6.1.2.x server, such as 22.214.171.124, 126.96.36.199 or 188.8.131.52. However, it can’t be applied to 6.1.1.x or 6.1.3.x.
Included in the ZIP file are the following files:
Notice that inside the cumulative patch ZIP file there is another ZIP file and a JAR file. These two files are the patch contents that need to be deployed to the server.
For both the new and old patch application processes, you must decompress the cumulative patch ZIP file to have access to the ZIP and JAR file that contain the patch.
Let’s compare the two processes. We will assume that the cumulative patch ZIP file has been downloaded and decompressed into a directory which is
You probably noticed that the main difference is having to make a backup of the ROOT directory and extracting the ZIP file into the ROOT directory. This is a major improvement, in that you no longer should be concerned with manually backing up and restoring the ROOT directory when applying a patch. Preserving previous data is handled by the server when starting the server.
Should something go wrong, backing out of a patch is as simple as applying a patch:
- Stop the server.
- Remove the JAR file from server/patches directory.
- Remove the ZIP file from server/patches/web directory.
- Start the server again.
Important: Ensure that only one set of patch files is applied to a server at any given time, having multiple active patches might cause CLASSPATH conflicts.