Upgrading databases to Synergy Release 7.1

About this task

This section explains how to upgrade your Rational Synergy databases to Rational Synergy Release 7.1 when using the procedure "Upgrading an Existing Server."

Perform these database upgrade steps:

Database upgrade requirements Before you can use your Release 6.4, 6.5, or 7.0 databases with Rational Synergy Release 7.1, you must upgrade these databases. Moreover, before you upgrade these databases, you must have installed Rational Synergy Release 7.1.

This section describes how to upgrade Rational Synergy 6.4, 6.5, or 7.0 base model databases: databases that have not been customized using a model install from a model database.

Databases customized using the Type Definition dialog box, or by modifying control files, and so on, are still considered base model databases. These databases must be upgraded using these procedures.

To upgrade model databases and databases that have been customized using a model install, contact IBM Rational Software Support.

Upgrading base model databases to 7.1 Perform the following steps for each Windows production database to be upgraded.

To upgrade base model databases to 7.1:

Procedure

  1. Log on to the server machine as the CM Administrator.
  2. Save manual customizations.

    The upgrade program automatically saves your previous pt and notify directories, and your previous Windows migrate.rul file.

    If you any database-specific configuration files, make a backup copy of the files to save the changes.

  3. Run the upgrade program.
    > ccmdb upgrade database_path1       databasepath2 . . . >logfile

    The database_path must be supplied as a UNC path.

    You can specify any number of database_path UNC paths for a list of databases to be upgraded. The upgrade program can take anywhere from a few minutes for a small database to many hours for a large database.

    For more details about the upgrade program, see " Running the Rational Synergy upgrade program" on page 73.

  4. The upgrade program unprotects the databases. Reprotect the databases, using ccmdb protect database_path, until you have completed the following steps and have tested the results.
  5. After the database upgrade is complete, look through the logfile that you created in 3 and the ccm_upgrade.log file created by the ccmdb upgrade command to locate any error messages or warnings that require further action.
  6. Restore manual customizations.

    If you changed any database-specific configuration files, such as triggers, merge the changes you saved in 2 into the converted databases.

    Note: You must merge these files with the Release 7.1 versions, not copy back your saved versions.
  7. Save the following directories to a separate directory for future reference.

    The ccmdb upgrade program saves selected files from your database before installing the new 7.1 files. After ccmdb upgrade completes for the first item on a database, save these files elsewhere to prevent them from being overwritten by future upgrades. The saved files reside under the database path.

    Save the content of the following directories:

    • old_types
    • oldbin
    • oldpt
    • lib/oldnotify

    Save the content of the following files:

    • lib/Unix/migrate.old
    • lib/Windows/migrate.old
  8. Modify standard types.

    If you modified any standard types in the database since the previous model install, they are automatically exported to the database_path\old_types directory. Compare any modified type with the corresponding Release 7.1 type as follows:

    1. Start Synergy Classic and use either the CLI or the GUI.
    2. Export the Release 7.1 type using the following command:
      ccm typedef /export type_name /dir to_path
    3. Compare the Release 7.1 type to the corresponding type that is in the
      database_path\old_types directory. Do so by comparing XML files.
    4. If you need to reapply changes, start a session on the upgraded database using Release 7.1, start the Type Definition dialog box, and reapply the changes. Do not perform a type definition import of the standard type from a prior release into the upgraded database without examining and understanding all the differences. In doing so, other properties of the type definition might revert to their definition from a prior release and these might be incompatible with Release 7.1.
  9. Merge task attribute customizations.

    Settings and possible values for some task attributes are held in the pt directory of your databases.

    After you have used these Upgrade Instructions to upgrade a database from Release 6.4, 6.5, or 7.0 to Release 7.1, you have 2 pt directories under that database. To complete the upgrade, you must reapply the changes you made in your previous release to the new database_path\pt directory. Your previous pt directory was saved in database_path\oldpt.

    Note: You must merge these files with the Release 7.1 versions, not copy back your saved versions.

    You must also remember to restore any changes you made to the task type, such as adding attributes to the source_attrs attribute.

  10. Merge notify customizations.

    After you have used these Upgrade Instructions to upgrade a database from Release 6.4, 6.5, or 7.0 to Release 7.1, you have 2 notify directories under that database. To complete the upgrade, you must reapply the changes you made in your previous release to the new database_path\notify directory. Your previous notify directory was saved in database_path\oldnotify.

    Note: You must merge these files with the Release 7.1 versions, not copy back your saved versions. It is important that you do this merge if you use Rational Change, because it requires modified notify scripts.
  11. Set site default settings.

    If you are using settings other than the default settings for the following options, you need to specify the defaults for your site. These settings apply across all sessions for all interfaces. Edit the following entries in the ccm.ini file to set defaults:

    baseline_template
    baseline_template_date_format
    baseline_template_repl_char
    include_required_tasks
    project_subdir_template
    wa_path_template

    For more information about these settings, see the Defaults section of the Synergy CLI Help, Web mode.

  12. Upgrade DCM settings.

    For complete information about upgrading a DCM database, see "Upgrading Synergy Distributed clusters" on page 85.

Results

Your database is now upgraded to Release 7.1.

Testing the database upgrade You have completed the upgrade to your production database. To test the result, start a Rational Synergy session and perform a number of operations. This topic contains a short list of operations.

If the database was manually protected after the upgrade, you must unprotect it before you can start a session. To run your tests, unprotect the database and start a session. Then, immediately protect the database again so that developers do not use the database until you have confirmed that it is working correctly. Repeat these steps each time you start a session for testing or for the post-upgrade actions described in Performing post-upgrade steps.

Start a Rational Synergy session on the upgraded database. On the Windows taskbar, click Start > All Programs > IBM Rational > IBM Rational Tools > IBM Rational Synergy 7.1 to display the Start Rational Synergy dialog box.

Test at least the following functionality in each upgraded database:

See " Considerations for upgrading to Synergy 7.1" on page 9 for detailed information about testing the upgrade.


Feedback