Repository tools command to apply a patch fix to all ELM applications on the server

Use the patchApplyGlobal command to apply a patch fix to all IBM Engineering Lifecycle Management (ELM) applications on the server.

Before you begin

Important: Use this command only when all ELM applications are at the same version.


The patchApplyGlobal command applies a patch fix to all ELM applications on the server. All product fixes for the ELM 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 ELM applications to clear the cache before you restart the server.


Attribute Description Required Default
file Path and file name of the patch archive file Yes Not applicable


This example shows how to apply a patch fix to the server:

Windows operating system icon Open a command prompt and enter this command:

repotools-jts.bat -patchApplyGlobal file=C:\tmp\

Linux operating system icon UNIX operating system icon Open a command line and enter this command: -patchApplyGlobal file=/tmp/


Linux operating system icon UNIX operating system icon 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:
On WebSphere® Application Server:
where the variables are:
WebSphere Application Server installation directory.
WebSphere Application Server profile name.
Application context. For example:
Application context Description
jts Jazz Team Server
ccm Change and Configuration Management
qm Quality Management
rm Requirements Management

If the log file contains messages that are related to permissions problems on the /patch folder or the file, change the permissions on these items to allow write access to the owner of the server process. Then, restart the server.