Repository tools command for finalizing the IBM Engineering Lifecycle Management applications migration
Use the finalizeApplicationMigration command to complete the offline migration of the Engineering Lifecycle Management applications.
Purpose
The finalizeApplicationMigration command finalizes a hybrid application migration. For the IBM® DOORS® Next application, this command adds the information from the previous friendsconfig.rdf file to the new Engineering Requirements Management DOORS Next application database.This command also removes any data that is specific to Jazz® Team Server from the cloned database and modifies the Engineering Requirements Management DOORS Next process areas so that the Engineering Requirements Management DOORS Next server can access them. You must run this command after you run the -addTables command during the manual DOORS application upgrade.
Parameters
| Attribute | Description | Required | Default |
|---|---|---|---|
| teamserver.properties | The path to the teamserver.properties file. The index directory is read from this location. | No | conf/application/teamserver.properties where application is jts, ccm, rm, qm, gc, dcc, or relm. |
| applicationId | The application ID of the application that is being migrated. The application ID is shown in the command window during the upgrade. Make a note of the application ID. When you are running this command on Jazz Team Server, you must provide the application ID that is being migrated with Jazz Team Server. The application ID is also logged in the logFile parameter. | No | None |
| repositoryURL | The public URL of the application that is being migrated. | No | None |
| checkOauthDomain | An argument that is run with the repotools-jts command only. When the checkOauthDomain argument is provided with the applicationId argument, the checkOauthDomain argument verifies that the application friend has Jazz Team Server in its list of OAuth domains. | No | False |
| logFile | The path to the log file. | No | repotools-application_finalizeApplicationMigration.log where application is jts, ccm, rm, qm, gc, dcc, or relm. |
| noPrompt | Does not prompt before finalizing the application migration. | No | N/A |
Example
The following example is for Jazz Team Server. To use
this command for other applications, run these options from the server directory:
- IBM Engineering Workflow Management (Change and Configuration Management application): repotools-ccm
- IBM Engineering Requirements Management DOORS Next (Requirements Management application): repotools-rm
- IBM Engineering Test Management (Quality Management application): repotools-qm
- Global Configuration Management: repotools-gc
- Data Collection Component: repotools-dcc
- IBM Engineering Lifecycle Optimization Engineering Insights: repotools-relm
Open a command prompt and enter this command:
Note: When
you run this command with the repotools-rm command,
do not specify the checkOauthDomain, applicationId,
or repositoryURL arguments. These arguments must
be specified only with the repotools-jts command.
cd C:\Program Files\IBM\JazzTeamServer\server\
repotools-jts.bat -finalizeApplicationMigration checkOauthDomain=true applicationId=RM-application-id repositoryURL=https://localhost:9443/rm
Open a command line and enter
this command:
cd /opt/IBM/JazzTeamServer/server/
./repotools-jts.sh -finalizeApplicationMigration checkOauthDomain=true applicationId=RM-application-id repositoryURL=https://localhost:9443/rm