Performing post-upgrade steps

Perform these tasks after your upgrade is complete.

About this task

Perform these post-upgrade steps:

Procedure

  1. Installing Rational Change 5.3 or later, if applicable
  2. Read Synergy Distributed transfers after upgrade, if applicable
  3. Disabling 7.0, 7.1, 7.1a, 7.2 or later services
  4. Installing Windows clients, if applicable
  5. Testing the Rational Synergy client
  6. Making databases available for use
  7. Checking query limits and accelerated attributes
  8. Update system level file name filters
  9. Troubleshooting

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 Rational Synergy 7.2 or later. For detailed instructions, see the installation documentation.

Procedure

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

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\Synergy\7.2x\etc\ptcli.cfg

Synergy Distributed transfers after upgrade

Rational Synergy 7.2 or later supports DCM transfers to and from releases 7.0, 7.1, 7.1a, 7.2 or later.

Procedure

Patches to these releases are required for DCM compatibility. For additional information, see the Rational Synergy Readme file for Release 7.2 or later and the product Readme files for patches to the earlier releases.

Disabling 7.0, 7.1, 7.1a, 7.2 or later services

About this task

After the upgrade process, disable the services on the server to make the previous release unusable.

To disable 7.0, 7.1, 7.1a, 7.2 or later services:

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, 7.1a, 7.2 or later Rational Synergy service:
    1. Right-click the service entry, and select Properties.
    2. In the General tab, change the Startup type to Disabled.
    Note: Do not delete the previous Rational Synergy installation directory. If you remove it incorrectly, your upgrade might be compromised.

Installing Windows clients

If needed, install Windows clients for Rational Synergy Release 7.2 or later.

Procedure

Install Windows clients for Rational Synergy Release 7.2 or later. You are not required to uninstall clients for previous releases. However, you can do so if you do not require access to the databases from the previous release. 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 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 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 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.

Update system level file name filters

The system level filters defined in the base model attribute 'system_filename_filters' in Synergy 7.0 and 7.1 if were updated to included 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 this step can be skipped.

Procedure

  1. Convert the system level filters that were updated on 'system_filename_filters' base model attribute other than the built-in once 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 below:

*.XYZ

The above filter should be converted using mapping rules syntax as below and the converted rule has to be updated on the base model attribute 'mapping_rules':

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

Troubleshooting

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 about the IBM® Rational Support site. This site also contains Frequently Asked Questions (FAQs), technical bulletins, and a Discussion Forum.
  2. If you still have questions, contact IBM Rational Software Support.

Feedback