Use this script to upgrade Data Collection Component.
LocationThe dcc_upgrade script upgrades all releases of Data Collection Component version 6 and later to version 7.0.1. Although the script file is in the upgrade/dcc directory, you must run it from the DCC_7.0.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.
The English and translated versions of the dcc_params files are in the DCC_7.0.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.
- 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.
|-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
By default, the parameter value is derived from the repotool -version command that runs against the old Data Collection Component application.
|-newApplicationHome||Path to the Data Collection Component application configuration directory of the new installation.||No||conf|
|-updateAppServerFiles||By default, this option is set to yes to update the Tomcat configuration files when
migrating to Liberty. Set this parameter to
noif you are using WebSphere® Application Server.
|-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|
|-oldApplicationTomcatHome||Full path to the Apache Tomcat home directory of the old Data Collection Component installation. By default, the -oldApplicationTomcatHome parameter is derived from the -oldApplicationHome parameter value.||No||N/A|
cd C:\Program Files\IBM\JazzTeamServer_7.0.1\server upgrade\dcc\dcc_upgrade.bat -oldApplicationHome OLD_DCC_install_dir\server\conf
cd /opt/IBM/JazzTeamServer_7.0.1/server ./upgrade/dcc/dcc_upgrade.sh -oldApplicationHome OLD_DCC_install_dir/server/conf