Performing post-upgrade steps

Learn about some of the things you might be required to do after your upgrade is complete.

About this task

  1. Installing Rational® Change 5.3 or later, if applicable
  2. Read Rational Synergy Distributed transfers after upgrade, if applicable
  3. Users might be required to Updating work areas
  4. When no longer needed, Removing the previous installation
  5. Updating ccm symbolic link, if applicable
  6. Installing Windows clients, if applicable
  7. Making databases available for use
  8. Checking query limits and accelerated attributes
  9. Troubleshooting postupgrade issues

Installing Rational Change 5.3 or later

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

Before you begin

You must create or upgrade at least one database before you install Rational Change , 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 2, merge it now. The ptcli file is: /usr/local/ccm72x/etc/ptcli.cfg

Rational Synergy Distributed transfers after upgrade

Rational Synergy 7.2 or later 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 more information, see the readme file for Release 7.2 or later and the product readme files for patches to the earlier releases.

For complete information about upgrading a DCM database, see Upgrading Rational Synergy Distributed clusters.

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.

Removing the previous installation

When you no longer need your old release, remove the previous installation.

About this task

Delete your old release directory only if you are sure that there are no other installations sharing part of this directory, perhaps through an NFS mount from another computer. For example, in heterogeneous installation, it is common to share the directory $CCM_HOME/etc.

Read Upgrade considerations to learn about more reasons for saving your previous installation.

Procedure

Run the following command to remove the previous installation:
$ su -
root# rm -rf /usr/local/ccm71
root# exit

Updating ccm symbolic link

To change the default version of Rational Synergy, delete any symbolic links to a previous release. Then, create a link to the new release.

Procedure

Run the following command:
$ su -
root# rm /usr/local/ccm
root# ln -s /usr/local/ccm72x /usr/local/ccm
root# exit

Installing Windows clients

If needed, install Windows clients. You are not required to uninstall clients for previous releases. However, you can do so if you do not require access any databases still using the previous release.

About this task

For detailed instructions, see the installation documentation.

Testing the Rational Synergy client

Test that the Rational Synergy client is functioning correctly.

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 returned information 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 with 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 postupgrade actions, your upgrade is complete.

Procedure

  1. If you protected the databases during the upgrade, test, or postupgrade 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 7.2 or later, text attributes are encoded in UTF-8, a variable-length encoding. The limit on queries has been raised from 64 bytes to 72 bytes. However, in UTF-8, a string that is represented by 64 or fewer characters and bytes in the CP1252 character encoding might require more than 72 bytes. You must review your queries to see if this issue is occurring.

Before you begin

Users upgrading from release 7.1a, you 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 releases 7.0 and 7.1. The same string takes up 74 bytes in the UTF-8 encoding used in 7.2 or later. 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 or later.

Troubleshooting postupgrade 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 on the IBM® Rational Support site.
  2. If you still have questions, contact IBM Rational Software Support.

Feedback