Repository tools command to apply a patch fix to all Engineering Lifecycle Management applications on the server
Use the patchApplyGlobal command to apply a patch fix to all IBM Engineering Lifecycle Management applications on the server.
Before you begin
Purpose
The patchApplyGlobal command applies a patch fix to all Engineering Lifecycle Management applications on the server. All product fixes for the Engineering Lifecycle Management applications are included in a single patch archive file. The new patch fix replaces any previous patch fixes that were applied to the server.
You can use this command whether the server is running or not. If the server is running, you must restart it to apply the patch fix. You do not need to reset the Engineering Lifecycle Management applications to clear the cache before you restart the server.
Parameters
| Attribute | Description | Required | Default |
|---|---|---|---|
| file | Path and file name of the patch archive file | Yes | Not applicable |
Example
This example shows how to apply a patch fix to the server:
Open a command prompt and enter
this command:
repotools-jts.bat -patchApplyGlobal file=C:\tmp\patch_file.zip
Open a command line and enter
this command:
repotools-jts.sh -patchApplyGlobal file=/tmp/patch_file.zip
Troubleshooting
If the patch fix does not appear
to be loaded when the server is restarted (for example, the patch
fix is not displayed in the Build Information section
of the Server Administration page for the Jazz® Team Server),
review the contents of the server log file:
Review logs under
<JAZZ_INSTALL_DIR>\server\logs\patch_application_context.log
- application_context
- Application context. For example:
Application context Description jts Jazz Team Server ccm Engineering Workflow Management qm Engineering Test Management rm IBM DOORS® Next
If the log file contains messages that are related to permissions problems on the /patch folder or the patch.properties file, change the permissions on these items to allow write access to the owner of the server process. Then, restart the server.