Migrating your repository

You can migrate your IBM Cloud application repository by following these steps:

About this task

Migrating your IBM Cloud application involves several steps, some of which you perform, some of which IBM Cloud support performs.

Procedure

  1. Perform a dry run or mock migration: You must first perform a mock migration or dry run for verification and testing. A mock migration can help in the planning of a production migration, and it gives you a better understanding of the time required to prepare for a production cut over. These are the tasks involved in a mock migration
    1. Export your data: Export times can take anywhere from an hour up to multiple days; large databases are more likely to have slow exports, for example, IBM® Engineering Requirements Management DOORS® Next databases.
    2. Upload and download data file
    3. Perform integrity checks
    4. Run validations and tests
  2. Create server backups: As a precaution, create server backups. If you are running virtualized servers, snapshots are sufficient.
    1. Stop all ELM application servers and their database servers.
    2. Back up or create snapshots of these servers.
  3. Create a folder to collect the Export results
    1. Create a temporary folder to store the exported file, The space required is larger than the current database size. To create a directory:
      • Windows: mkdir C:\tmp\export\
      • Linux: mkdir /tmp/export/
  4. Run integrity checks for exporting data
    1. Jazz Online Verify Tool: Run the online verify tool check If possible install and run the Jazz Online Verify Tool, (download and instructions here). This takes awhile to run (see link FAQ ), but the servers do not need to be shut down to run this.
    2. Repotools –Verify command: Run the Repotools –Verify command: This must be a level-10 data integrity check. The check must be run for every available IBM Engineering Workflow Management (ELM) application, for example:
      • IBM Change and Configuration Management
      • IBM Jazz® Team Server
      • IBM Engineering Workflow Management (EWM)
      • IBM Engineering Lifecycle Optimization - Method Composer (MEC)
      • IBM Engineering Test Management (ETM)
      • Global Configuration
      • IBM Engineering Lifecycle Optimization - Engineering Insights (ENI)

      In these examples replace jts with each application name. These examples assume a default ELM installation: Make sure that you save the log files:

      • Windows:
        cd C:\Program Files\IBM\JazzTeamServer\server\
        repotools-jts.bat -verify teamserver.properties=conf\jts\teamserver.properties level=10

        logFile=logFile=C:\tmp\export\jts_verification.txt

      • Linux:
        cd /opt/IBM/JazzTeamServer/server/
        ./repotools-jts.sh -verify teamserver.properties=conf/jts/teamserver.properties level=10

        logFile=logFile=/tmp/export/jts_verification.txt

      For more information, see Repository tools command to export the contents of a database
  5. Perform the export
    1. Run the following command for every application that contains data: IBM Jazz Team Server, IBM Rational Change and Configuration Management, MEC, ETM, Global Configuration, ENI. Any repotools export that is not provided is assumed to be a green-field (new or empty) database. In the examples below, replace jts with each application name. These examples assume a default ELM installation: Make sure that you save the log files:
      • Windows:
        cd C:\Program Files\IBM\JazzTeamServer\server\
        repotools-jts.bat -export toFile=C:\tmp\export\jts_export.tar
        teamserver.properties=conf\jts\teamserver.properties

        logFile=C:\tmp\export\jts_export_log.txt

      • Linux:
        cd opt/IBM/JazzTeamServer/server/
        ./repotools-jts.sh -export toFile=/tmp/export/jts_export.tar
        teamserver.properties=conf/jts/teamserver.properties 

        logFile=/tmp/export/jts_export_log.txt

      For more information, see Repository tools command to export the contents of a database
  6. Compress the conf folder
    1. Next, compress the conf into a .tar or a .zip file. These folders can be many gigabytes in size. Indices are regenerated during or after the import. Therefore, the conf/ folder is very large, and this can mean long upload and download times. The application indices folders can be deleted if necessary. In a default ELM installation, all applications are nested inside the conf/ path. Include user information in the upload: Use the eExportUsers command to export the user information into a CSV file and include this CSV file in the upload:
    • Windows: In Windows Explorer, browse to C:\Program Files\IBM\JazzTeamServer\server\. Right click the conf/ folder, and select Send To > Compressed (zipped) folder.
    • Linux:
      cd /opt/IBM/JazzTeamServer/server/
      tar cvfz /tmp/export/conf_folder.tar.gz conf/
  7. Transfer or upload the export results
    1. Export your compressed file using SFTP, and include the following files:
      • IBM Jazz Team Server
      • IBM Rational® Quality Manager
      • MEC
      • Change and Configuration Management
      • verify_logs.zip
      • export_logs.zip
      • users.zip
      • conf.zip
      Note: If your SFTP requires a password, include the password in your export file.
  8. Communication during the mock and production migrations
    1. The cloud engineers use their support ticketing system to raise a migration ticket and add you (and your IBM technical contact). As work progresses you will receive updates in emails titled [Service Desk].