Repository tools command to apply a patch fix to an IBM Engineering Lifecycle Management application
Use the patchApplyApp command to apply a patch fix to an IBM® Engineering Lifecycle Management (ELM) application on the server.
Purpose
Use this command to apply a patch fix to a single ELM application on the server. The new patch fix replaces any previous patches that were applied to the application.
You can use this command whether the server is running or not. If the server is running, you must restart the application to enable the patch fix. You do not need to reset the application to clear the cache before you restart the application.
Application-level patch fixes take precedence over global patch fixes. If you apply both application-level patch fixes and a global patch fix, the application-level patch fixes are used.
Parameters
| Attribute | Description | Required | Default |
|---|---|---|---|
| file | Path and file name of the patch fix archive file | Yes | Not applicable |
| app | The application context in which to apply the patch fix. For example, to run this
command for the Change and Configuration Management application, set the value of
app to ccm:
repotools-jts.bat -patchApplyApp file=C:\tmp\patch-fix.zip app=ccm |
No | If the app parameter is omitted,
the command is applied to the application that is associated with
the repository tools command. For example, the following command
will apply the patch fix to the Change and Configuration Management
application:
repotools-ccm.bat -patchApplyApp The
next two commands are functionally equivalent:
repotools-ccm.bat -patchApplyApp file=C:\tmp\patch-fix.zip repotools-jts.bat -patchApplyApp file=C:\tmp\patch-fix.zip app=ccm |
Example
This example shows how to individually apply an ELM patch fix to each application on the server.
Open a command prompt and enter
these commands:
repotools-jts.bat -patchApplyApp file=C:\tmp\patch_file.zip repotools-jts.bat -patchApplyApp file=C:\tmp\patch_file.zip app=ccm repotools-ccm.bat -patchApplyApp file=C:\tmp\patch_file.zip repotools-qm.bat -patchApplyApp file=C:\tmp\patch_file.zip repotools-rm.bat -patchApplyApp file=C:\tmp\patch_file.zip
Open a command line and enter
these commands:
repotools-jts.sh -patchApplyApp file=/tmp/patch_file.zip repotools-jts.sh -patchApplyApp file=/tmp/patch_file.zip app=ccm repotools-ccm.sh -patchApplyApp file=/tmp/patch_file.zip repotools-qm.sh -patchApplyApp file=/tmp/patch_file.zip repotools-rm.sh -patchApplyApp 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 log file:- On WebSphere® Application Server:
- WebSphere_installation_directory/profiles/profile_name/logs/patch_application_context.log
- WebSphere_installation_directory
- WebSphere Application Server installation directory.
- profile_name
- WebSphere Application Server profile name.
- application_context
- 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 patch.properties file, change the permissions on these items to allow write access to the owner of the server process. Then, restart the server.