r10 - 2015-05-27 - 17:04:35 - Main.sbagotYou are here: TWiki >  Deployment Web > DeploymentTroubleshooting > UpgradeTroubleshooting > CLMUpgradeTroubleshooting > UpdateConfigurationFiles

Update configuration files (CCM, QM, JTS)

Authors: UpgradeTroubleshootingTeam
Build basis: CLM 4.x

This topic discusses the first step in the upgrade which updates the configuration files for each application.


During this step in the upgrade process, a log file appended with _migration__updateConfigurationFiles will be created in the ../server directory of the Collaborative Lifecycle Management (CLM) application installation directory. An example of this file is:

Known Issues

Below are some known issues which arise during the update configuration files step in the upgrade process

Errors which can occur with any CLM application

This section will discuss errors common when updating configuration files which can occur with any of the CLM applications.

"The version string is not properly formatted" error

Version: Upgrade to 4.x
Error During Upgrade: The version string " -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true" is not properly formatted. java.lang.IllegalStateException: The version string " -Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true" is not properly formatted.
Cause: The 3.x jazzTeamServer directory was renamed to x_orig and its old name was used for 4.0. There could be some files got corrupted during the folder rename process
Resolution: Ensure that the original directory name is kept and install 4.0 in a new jazz home location. Keep both folders separate.

Related topics:

External links:

  • None

Additional contributors: SusanWu

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r10 < r9 < r8 < r7 < r6 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.