dcc_upgrade script

Use this script to upgrade Data Collection Component.

Location

The dcc_upgrade script upgrades all releases of Data Collection Component version 5 and 6 to version 6.0.6.1. Although the script file is in the upgrade/dcc directory, you must run it from the DCC_6.0.6.1_INSTALL_DIR/server directory. When you run the script, if the file path contains spaces, ensure that you enclose the path name in double quotation marks. Enter [E] to execute the command, [S] to skip a step, or hit [Enter] to cancel the script execution.
Tip: As an alternative to running the script and all its command-line arguments, you can open the script's parameters file, modify the default values, and run an abbreviated form of the command line.

The English and translated versions of the dcc_params files are in the DCC_6.0.6.1_INSTALL_DIR/server/upgrade/dcc/params directory. Open dcc_params or a translated version of the file, and specify values for each parameter. You must set the path parameter to point to the OLD_APPLICATION_HOME directory, which must be an existing directory whose name ends with server/conf.

Purpose

The script performs the following steps:
  • Step 0: Runs the -migration_dcc_updateConfigurationFiles command that updates the server configuration files. After the configuration files are merged successfully, enter [C] to continue. An editor opens in which you can verify the Data Collection Component application teamserver.properties file. Verify that the Public URI root denoted by the com.ibm.team.repository.server.webapp.url property is correct. Also verify that the database properties are correct. When done, save your changes, if any, and close the editor to continue the script execution.
  • Step 1: Adds tables to the DCC repository database.

Parameters

Attribute Description Required Default
oldApplicationHome Full path to the old Data Collection Component application configuration directory of the old installation. The path must not contain any spaces. In a typical installation, this path is OLD_DCC_INSTALL_DIR/server/conf. Yes none
applicationContextRoot Data Collection Component context root. No dcc
oldApplicationVersion The version of Data Collection Component that is being upgraded.

By default, the parameter value is derived from the repotool -version command that runs against the old Data Collection Component application.

No none
newApplicationHome Path to the Data Collection Component application configuration directory of the new installation. No conf
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. Set this parameter 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
oldApplicationTomcatHome This is a graphical icon for Tomcat. Full path to the Apache Tomcat home directory of the old Data Collection Component installation. By default, the parameter value is derived from the oldApplicationHome parameter value. No none
newApplicationTomcatHome This is a graphical icon for Tomcat. Path to the Data Collection Component Apache Tomcat home directory of the new installation. By default, the parameter value is derived from the newApplicationHome parameter value. This parameter must be provided if upgrading in Apache Tomcat and Tomcat is installed in a separate directory than ELM. No none
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
noPrompt Do not prompt before creating or modifying the tables. No none
noVerify Do not perform teamserver.properties file verification. No none
overwrite Whether to overwrite any existing file. No no
noStepPrompt Do not prompt before executing a step. No false
noEditor The -noEditor parameter eliminates opening an editor during the execution of the upgrade script to review or modify the teamserver.properties file. The -noEditor parameter in conjunction with -noStepPrompt, -noVerify, and -noPrompt parameters can be used for a fully automated upgrade script without any user interactions. If you need to review or modify the teamserver.properties file during the upgrade, such as in a WebSphere Application Server environment where the index location might be relative to the profile directory, do not use this parameter. No false

Example

This is a graphical icon for Windows.
cd C:\Program Files\IBM\JazzTeamServer_6.0.6.1\server
upgrade\dcc\dcc_upgrade.bat -oldApplicationHome "C:\Program Files\IBM\JazzTeamServer_5.0.x\server\conf"
This is a graphical icon for Linux.
cd /opt/IBM/JazzTeamServer_6.0.6.1/server
./upgrade/dcc/dcc_upgrade.sh -oldApplicationHome "/opt/IBM/JazzTeamServer_5.0.x/server/conf" 
This is a graphical icon for WebSphere Application Server. If you are using WebSphere Application Server, add:
-updateTomcatFiles no

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