Performing post-upgrade steps

This section explains in detail some things you might be required to do after your upgrade is complete.

About this task

  1. Installing Rational Change 5.3, if applicable
  2. Read Rational Synergy Distributed transfers after upgrade, if applicable
  3. Users might require Updating work areas
  4. When no longer needed, Disabling 7.0, 7.1, or 7.1a services
  5. When no longer needed, Removing the previous installation
  6. Installing Windows clients, if applicable
  7. Testing the Rational Synergy client
  8. Making databases available for use
  9. Checking query limits and accelerated attributes
  10. Updating the system level file name filters
  11. Troubleshooting post-upgrade issues

Installing Rational Change 5.3

If you use Rational Change with this database, install Rational Change 5.3. Earlier releases of Rational Change are not compatible with Rational Synergy 7.2. For detailed instructions, see the installation documentation.

Before you begin

You must create or upgrade at least one database before you install Rational Change 5.3, because Rational Change requires access to a Rational Synergy database.

Procedure

If you use Rational Change, and if you saved a modified copy of the previous ptcli configuration file as described in Saving the previous installation, merge it at this time. The ptcli file is: Program Files\IBM Rational\IBM Rational Synergy 7.2\etc\ptcli.cfg

Rational Synergy Distributed transfers after upgrade

Rational Synergy 7.2 supports DCM transfers to and from releases 7.0, 7.1, or 7.1a. Patches to these releases are required for DCM compatibility.

About this task

For additional information, see the Rational Synergy Readme file for Release 7.2 and the product Readme files for patches to the earlier releases.

Updating work areas

If you moved the database to a new path (perhaps on a new computer) as part of the upgrade, update existing work areas so that they reference the new path. This information is true for both copy-based and link-based work areas.

Procedure

  1. Each user of a moved database must run the command to update their working projects:
    ccm wa /dbpath old_database_path /show project_spec...
    ccm wa /dbpath old_database_path /replace -show project_spec...
    1. Build managers must also update their prep projects.
  2. Update shared or static projects by using the appropriate /scope options to the ccm wa /dbpath command.

Disabling 7.0, 7.1, or 7.1a services

The upgrade process stopped and rendered unusable the previous release on the upgraded server.

Procedure

  1. On the taskbar, click Start > Control Panel > Administrative Tools > Services to open the Services window.
  2. Repeat the following steps for each 7.0, 7.1, or 7.1a Rational Synergy service:
    1. Right-click the service entry, and select Properties.
    2. In the General tab, change the Startup type to Disabled.

Removing the previous installation

When you no longer need your old release, use the uninstall command to remove the previous installation.

About this task

Note: Do not delete the previous Rational Synergy installation directory if you used the procedure "Upgrade an Existing Server" on this computer. If you remove it incorrectly, your upgraded server might be compromised. For more information, contact IBM® Rational Software Support.

Installing Windows clients

If needed, install Windows clients for Rational Synergy Release 7.2. You are not required to uninstall clients for previous releases. However, you can do so if you do not require access to the databases that use the previous release.

About this task

For detailed instructions, see the installation documentation.

Testing the Rational Synergy client

Test the Rational Synergy client with your upgraded database.

Procedure

  1. Run the ccm monitor command and check that the appropriate CCM server is running. If it is not, start it using the ccm_server command. Note the server URL shown in the output after running the ccm monitor command.
  2. In your browser, type protocol://server:port/admin, where the protocol (http or https), server and port are in the server URL.
  3. When prompted, type the administrator password.
  4. On the Databases tab, check that the database you want to test is listed as connected to this server. If it is shown as connected to a different server, either use the other server, or use the web page to change the server for the database.
  5. Start a Rational Synergy session by using the server URL you have verified:

    cmsynergy /d database_path [/s server_url]

    Note: The s option for specifying the server URL is optional. In most cases, it is not needed, and the server URL is automatically determined via the Rational Synergy router.

Making databases available for use

After you have completed the upgrade, tested the results, and performed any required post-upgrade actions, your upgrade is complete.

Procedure

  1. If you protected the databases during the upgrade, test, or post-upgrade process, unprotect them now.
  2. Tell the users that the databases are ready for use.
  3. Upgrade the client software of the users.

Checking query limits and accelerated attributes

In Rational Synergy 7.0 and 7.1, string and text attributes were encoded in Windows CP1252, a single-byte encoding, and queries for string or text attributes examined only the first 64 characters (bytes) of each string. In Rational Synergy 7.2, text attributes are encoded in UTF-8, a variable-length encoding. The limit on queries has been raised from 64 bytes to 72 bytes, but it is possible that a string that is represented by 64 or fewer characters and bytes in CP1252 requires more than 72 bytes in UTF-8. Users must review their queries to see if this issue is occurring.

Before you begin

Users upgrading from Rational Synergy 7.1a can skip this task.

Procedure

  1. Review queries for strings that did not encode properly.
  2. Make the attributes accelerated to resolve the issue. Accelerated attributes have a query limit of 700 bytes.

Example

The string “ééééééééééééééééééééééééééééééééééééé” (37 e-acute Latin-1 characters) takes up 37 bytes in the CP1252 encoding used in Rational Synergy 7.0 and 7.1. The same string takes up 74 bytes in the UTF-8 encoding used in Rational Synergy 7.2. As a result, a query for objects with some attribute equal to this value succeeds in 7.0 and 7.1, but fails in 7.2.

Updating the system level file name filters

If the system level filters defined in the base model attribute 'system_filename_filters' in Synergy 7.0 and 7.1 were updated to include any new filters other than the built-in filters, then they need to be defined in the base model attribute 'mapping_rules' using the mapping rules syntax.

Before you begin

If the 'system_filename_filters' base model attribute was not updated in previous releases of Synergy, then you can skip this step.

Procedure

  1. Convert the system level filters that were updated on 'system_filename_filters' base model attribute other than the built-in ones to mapping rules syntax.
  2. Update the rules created in the previous step on the 'mapping_rules' base model.

Example

If there is a filter on the base model attribute 'system_filename_filters' as shown in this example:

*.XYZ

Then you should convert this filter by using the mapping rules syntax as shown in this example, and the converted rule has to be updated on the base model attribute 'mapping_rules':

WHEN %name =~ '.*\\.XYZ' IGNORE

Troubleshooting post-upgrade issues

If you have difficulties with a command or process, or if you receive an error message that you do not understand, try these troubleshooting steps.

Procedure

  1. See the troubleshooting information, which is located on the IBM Rational Support site.
  2. If you still have questions, contact IBM Rational Software Support.

Feedback