Repository tools command to update the Quality Management application configuration files

Use the migration_qm_updateConfigurationFiles command to update migration configuration files.

Purpose

The migration_qm_updateConfigurationFiles command can be used to update configuration files from previous version to a new version. This command is used in an environment where the upgrade wrapper script cannot be used. The upgrade wrapper script includes this command and automates some of the manual steps. For information about the upgrade process and to generate an upgrade guide, see Interactive upgrade guide.
Important: You must shut down the server before you run the command. Also if your paths contain spaces, ensure you enclose them in double quotation marks.

Parameters

Attribute Description Required Default
oldApplicationHome Full path to the Quality Management home directory in the previous installation. For a typical installation, this path is QM_installation/server/conf. Yes N/A
applicationContextRoot Quality Management context root. No qm
updateTomcatFiles Whether to update the Apache Tomcat configuration files or migrate to WebSphere Liberty. Set this parameter to no if you are using WebSphere® Application Server and set it to yes if you are using Apache Tomcat. Starting in version 6.0.1, the default value has changed to no to automatically migrate Tomcat configuration files to WebSphere Liberty. No no
updateAppServerFiles By default, this option is set to yes to update the Tomcat configuration files when migrating to Liberty. Set this parameter to no if you are using WebSphere Application Server. If you are using Tomcat, this parameter will be ignored. No yes
oldTomcatHome Full path to the Tomcat root directory in previous version installation. By default, the oldTomcatHome parameter value is derived from the oldApplicationHome parameter. No none
newApplicationHome Full path to the application home directory in the new version installation. No conf
newJTSHome Path to the Jazz Team Server configuration directory of the new version installation. By default, the newJTSHome parameter value is derived from the newApplicationHome parameter value. No none
jtsContextRoot The new version Jazz Team Server context root. No jts
newApplicationTomcatHome Path to the Quality Management Tomcat home directory in the new version installation. By default, the newApplicationTomcatHome parameter value is derived from the newApplicationHome parameter. This parameter must be provided if upgrading in Apache Tomcat and Tomcat is installed in a separate directory than IBM® Engineering Lifecycle Management (ELM). No none
newJTSTomcatHome Path to the new version Jazz Team Server Tomcat home directory. By default, the newJTSTomcatHome parameter value is derived from the newJTSHome parameter. No none
ignoreJTSVersionCheck Do not attempt to verify that the application version is compatible with the Jazz Team Server version located at newJTSHome. This argument should only be used in a distributed deployment where the Jazz Team Server is on a separate system that is inaccessible from the application system. No N/A
logFile Path to the log file. No repotools-qm_qm_updateConfogurationFiles.log

Example

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

cd C:\Program Files\IBM\JazzTeamServer\server\
repotools-qm.bat -migration_qm_updateConfigurationFiles oldApplicationHome="C:\Program Files\IBM\OLD_VERSION_QM\server\conf"

For Unix operating systems Open a command line and enter this command:

cd opt/IBM/JazzTeamServer/server/
./repotools-qm.sh -migration_qm_updateConfigurationFiles oldApplicationHome=opt/IBM/OLD_VERSION_QM/server/conf

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki