Rational Synergy Interim Fix 3 for 7.1.0.7

Downloadable files


Abstract

IBM Rational Synergy 7.1.0.7_iFix003 has been made generally available and contains fixes to version 7.1.0.7.

Download Description

Table of Contents
Sections Description

The Change history section provides an overview on what is new in this release with a description of any new functions or enhancements when applicable.

The How critical is this fix section provides information related to the impact of this release to allow you to assess how your environment may be affected.

The Prerequisites section provides important information to review prior to the installation of this release.

The Download package section provides the direct link to obtain the download package for installation in your environment.

The Installation instructions section provides the installation instructions necessary to apply this release into your environment.

The Known side effects section contains a link to the known problems (open defects) identified at the time of this release.

Supporting Documentation
Document Description

Click to review the detailed system requirements information for a complete list of hardware requirements, supported operating systems, prerequisites and optional supported software, with component-level details and operating system restrictions.

This document contains a collection of product documentation links for IBM Rational Synergy prior to the creation of the IBM Knowledge Center.

Click to review a complete list of the defects (APARs) resolved in this release including a list of resolved defects for the entire version family.

Find technical developer content and resources.

Prerequisites

Installation Instructions

Review the installation guide in the Rational Synergy Documentation Library.

Table of contents:


Where to Apply this iFix

Apply this iFix to all Synergy installations (CCM_HOME) and clients. First install to the machine where the Synergy router daemon is running, then install to other server machines, and finally deploy to client machines.

Deliverable Synergy Components Affected

Those marked with an asterisk (*) have changed since 7.1.0.7_iFix002.

Database files affected by the iFix:

Database_path/lib/apilib.a
Database_path/lib/baselib.a
Database_path/lib/csetlib.a
Database_path/lib/focilib.a
Database_path/lib/ptlib.a

CCM_HOME files affected by the iFix:

All Platforms:

CCM_HOME/etc/cli/xml/mode6.5/update_urls.xml
CCM_HOME/jetty/webapps/jsp/task_properties.jsp
CCM_HOME/jetty/webapps/images/cmlauncher.jar
CCM_HOME/lib/cslib.a
CCM_HOME/lib/adminlib.a
* CCM_HOME/lib/eislib.a
CCM_HOME/lib/rfclib.a
* CCM_HOME/lib/ccmjava.jar
CCM_HOME/lib/crtool_rtc.jar
CCM_HOME/lib/aspectjrt.jar
CCM_HOME/lib/NetscapeBer.jar
CCM_HOME/lib/tdscommonlib.jar
CCM_HOME/lib/tdscryptolib.jar
CCM_HOME/lib/tdsjndilib.jar
CCM_HOME/lib/tdsloggerlib.jar
CCM_HOME/etc/ccm.crtool.rtc.properties
CCM_HOME/etc/TDSConfiguration.xml
CCM_HOME/etc/TDSResource_en_US.xml
CCM_HOME/etc/ccm.properties
CCM_HOME/etc/CcmError.properties

UNIX:

CCM_HOME/bin/ccm_server
CCM_HOME/bin/setup_rtc
* CCM_HOME/bin/setup_client_rtc_user
CCM_HOME/bin/util/ccm_util
* CCM_HOME/bin/dbutil/ccmdb_recocover_inf
CCM_HOME/lib/ccm_files

Microsoft Windows:

CCM_HOME\bin\setup_rtc.bat
* CCM_HOME\bin\setup_client_rtc_user.bat
CCM_HOME\bin\util\ccm_ess.exe
CCM_HOME\bin\util\ccm_objreg.exe
CCM_HOME\bin\util\ccm_router.exe
CCM_HOME\bin\util\ccm_websrv.exe

Installation Instructions on UNIX


Before you begin, make sure that you have performed a successful backup of your Synergy installation areas.

This iFix contains modifications to the software that must be installed in the installation directory (CCM_HOME changes).

Once you have installed 7.1.0.7 iFix003, do not install any individual iFix that does not clearly state that it may be installed on top of 7.1.0.7 iFix003, unless informed otherwise by Synergy Support.

  1. To install this iFix on UNIX, use the ccm_patch script. If you do not have the ccm_patch script, download it from the Synergy Support web site. If you have previously downloaded a copy of ccm_patch, please check to see if it is still the most up to date version. If not, download the latest version and discard your previous version. At the time of writing, the latest version of ccm_patch is 47.

    If you have downloaded a newer version, then copy the ccm_patch script to $CCM_HOME/bin in each server installation; make sure it is owned by ccm_root and has execute permission (mode 0755).



  2. In preparation for the following steps, ask all users to exit their Synergy sessions.

  3. If Rational Change or Rational Synergy Integrations are running, shut them down.

  4. Login as user ccm_root and set CCM_HOME to point to your Synergy installation.
    Shut down all Synergy 7.1 databases. Verify that all users have exited by using the ccm monitor command.

    $ su - ccm_root
    ccm_root$ CCM_HOME=/usr/local/ccm71 # Adjust as appropriate
    ccm_root$ PATH=$CCM_HOME/bin:$PATH
    ccm_root$ export CCM_HOME PATH
    ccm_root$ ccmdb shutdown <dbpath> # Repeat per database
    ccm_root$ ccm monitor

    Stop the Synergy daemons using the ccm_stop_daemons command.

      ccm_root$ ccm_stop_daemons

  5. Update the Synergy installation directory.

    Use the ccm_patch command. The argument to ccm_patch is the full path to the iFix file that you are installing.

    Note that ccm_patch must be run as root, since it needs to set ownership and permissions on the patched files.

      ccm_root$ su
    # CCM_HOME=/usr/local/ccm71 # Adjust as appropriate
    # PATH=$CCM_HOME/bin:$PATH
    # export CCM_HOME PATH


    If your database runs on Oracle then set ORACLE_HOME.

          # ORACLE_HOME=/usr/local/oracle # Adjust as appropriate
    # export ORACLE_HOME

    # ccm_patch <PATH>/7.1.0.7-RATL-RATISYNE-UNIX-IF003.tar.gz
    # exit

    Repeat this command for each installation directory.

    Once the installation directory has been updated, restart the Synergy daemons as the ccm_root user.

    ccm_root$ ccm_start_daemons

  6. Use the ccm_patch command to apply this iFix to one or more databases.

    If you have a customized model using a custom model database, contact Synergy Support for assistance.

    Databases that were shut down in step 3 must be unprotected prior to patching.

    $ su - ccm_root
    ccm_root$ CCM_HOME=/usr/local/ccm71 # Adjust as appropriate
    ccm_root$ PATH=$CCM_HOME/bin:$PATH
    ccm_root$ export CCM_HOME PATH
    ccm_root$ ccmdb unprotect <dbpath>
    ccm_root$ ccm_patch -dbonly $CCM_HOME/patches/7.1.0.7.003 <dbpath>.

  7. Inform users to restart Synergy sessions.

    This iFix contains a Windows client component. Users of Synergy Windows GUI will be prompted to download the iFix when a session is started. Users of the Windows CLI will be requested to patch the clients by browsing to
    http://<helpserver>:<port#>/client/Update_7.1-0.7.003.exe


    Alternatively, the executable, Update_7.1-0.7.003.exe, can be distributed to Windows CLI users, so you can execute it directly, to update you client installations.


Reversing the iFix on UNIX

If it is necessary to remove the iFix after it was installed, follow these steps.

  1. In preparation for the following steps, ask all users to exit their Synergy sessions. As 'ccm_root', shut down all Synergy databases that use this installation. Verify that all users have exited by using ccm monitor.

    $ su - ccm_root
    ccm_root$ CCM_HOME=/usr/local/ccm71 # Adjust as appropriate
    ccm_root$ PATH=$CCM_HOME/bin:$PATH
    ccm_root$ export CCM_HOME PATH
    ccm_root$ ccmdb shutdown <dbpath> # Repeat per database
    ccm_root$ ccm monitor

    Stop the Synergy daemons using the ccm_stop_daemons command.

    ccm_root$ ccm_stop_daemons

  2. Restore the installation files from before 7.1.0.7 iFix003.

    $CCM_HOME contains a save directory structure that contains all files that were removed or replaced during the iFix installation process. The files are saved with a suffix of _p7.1.0.7.003. In addition, the first time a particular file is saved it will also be saved with an extension of _orig. Replace all files that were updated with this iFix. For a complete list of $CCM_HOME files that were changed see section Deliverable Synergy Components Affected.

    For example $CCM_HOME/lib/ccmjava.jar was replaced. To replace it with the file from before this iFix:

    $ su - ccm_root
    ccm_root$ CCM_HOME=/usr/local/ccm71 # Adjust as appropriate
    ccm_root$ PATH=$CCM_HOME/bin:$PATH
    ccm_root$ export CCM_HOME PATH
    ccm_root$ cp $CCM_HOME/save/lib/ccmjava.jar_p7.1.0.7.003 \
    $CCM_HOME/lib/ccmjava.jar


    Repeat this step for each $CCM_HOME file listed in Deliverable Synergy Components Affected.

  3. Remove entries in patches.txt and patches.dat

    In the $CCM_HOME/etc directory are files patches.txt and patches.dat. Using an editor, for instance vi, edit these files.
    Remove the lines referencing this iFix.

    Save this file and exit the editor. If the resulting files are empty then delete them.

  4. Remove the file $CCM_HOME/etc/cli/xml/mode6.5/update_urls.xml from the run area if the run area is updated from 7.1.0.7.

  5. Login as user root. You need to run $CCM_HOME/bin/ccm_install in order to reset the ownership and permissions of the original files you copied back:

    $ su -
    # CCM_HOME=/usr/local/ccm71 # Adjust as appropriate
    # PATH=$CCM_HOME/bin:$PATH
    # export CCM_HOME PATH

    If your database runs on Oracle then set ORACLE_HOME

    # ORACLE_HOME=/usr/local/oracle # Adjust as appropriate
    # export ORACLE_HOME

    # ccm_install -c
    # exit

  6. Reverse 7.1.0.7 iFix003 in databases.

    If you have a customized model, using a model database, reinstate your previous model by performing a model install from your original customized model project to each database.

    Each database directory contains a save directory structure that contains all files that were removed or replaced during the iFix installation process. The files are saved with a suffix of _p7.1.0.7.003. In addition, the first time a particular file is saved it will also be saved with an extension of _orig. All files that were updated with this iFix should be replaced. For a complete list of database files that were changed see section .

    For example <dbpath>/lib/baselib.a was replaced, to replace it with the file from before this iFix:

    $ su - ccm_root
    ccm_root$ CCM_HOME=/usr/local/ccm71 # Adjust as appropriate
    ccm_root$ PATH=$CCM_HOME/bin:$PATH
    ccm_root$ export CCM_HOME PATH
    ccm_root$ cp <dbpath>/save/lib/baselib.a_p7.1.0.7.003 <dbpath>/lib/baselib.a

    Repeat this step for each database file listed in ..

    In the database path/db directory of each database is a file named MDL_INFO. Using an editor, for instance vi, edit these files. Remove the lines referencing this iFix.

    In the <database path>/etc directory of each database is a file named patches.dat. Using an editor, for instance vi, edit these files. Remove the lines referencing this iFix.

    Save these files and exit the editor. If the resulting files are empty then they should be deleted.

  7. Unprotect the databases that were shut down in step 1, using:

    ccm_root$ ccmdb unprotect <dbpath>

    Repeat for every database that was patched.

  8. Start the Synergy daemons using the ccm_start_daemons command.

    ccm_root$ ccm_start_daemons

  9. Inform users to restart Synergy sessions.


Installation Instructions on Microsoft Windows


Before you begin, make sure that you have performed a successful backup of your Synergy Installation areas.

This iFix contains modifications to the software that must be installed in the installation directory (CCM_HOME changes).

Once you have installed 7.1.0.7 iFix003, do not install any individual iFix that does not clearly state that it may be installed on top of 7.1.0.7 iFix003, unless informed otherwise by Synergy Support.

  1. Request that all users exit their Synergy sessions before you begin the installation. Shutdown all Synergy databases using the ccmdb shutdown command. Verify that all users have exited by using the ccm monitor command.

    > ccmdb shutdown <dbpath> # Repeat per database
    > ccm monitor

  2. If Rational Change or Rational Synergy Integrations are running, shut them down.

  3. To apply the iFix to a Windows Synergy server installation, you must log in as a user in the Local Administrator group on the Main or Additional server machine. Do not install the iFix on your computer if you use a shared network installation; just install the iFix once on the network installation.

  4. Once you have logged in as the appropriate user, run the iFix executable, 7.1.0.7-RATL-RATISYNE-Windows-IF003.exe from the command prompt or by double clicking it. This brings up the Patch Installation Utility which guides you through the steps of installing the iFix.
  5. Patch standard databases.

    If you do not have a customized model, apply this iFix to each of your databases. ALL databases must be patched prior to use with this iFix.

    If you have a customized model using a custom model database, contact Synergy Support for assistance.

    To patch a database on a Windows server, use the batch script that was extracted when you ran the self-extracting patch executable on the server. This script needs to be given the database path of the database(s) to be patched.

    Log in as "CM administrator" on the Main or Additional Server machine for the database being patched, and bring up a command window. Repeat the following commands for each database:

    > set CCM_HOME=c:\ccm71 # Adjust as appropriate
    > set PATH=%CCM_HOME%\bin;%PATH%
    > ccmdb unprotect <dbpath>
    > ccmdb_patch_7107_003 <dbpath>

  6. Inform users to restart Synergy sessions.


This iFix contains a Windows client component. Users of the Synergy Windows GUI will be prompted to download the iFix when a session is started. Users of the Windows CLI will be requested to patch the clients by browsing to:

http://helpserver:port#/client/Update_7.1-0.7.003.exe.

Alternatively, the executable, Update_7.1-0.7.003.exe, can be distributed to Windows CLI users, so they can execute it directly, to update their client installations.


Reversing the iFix on Microsoft Windows


If it is necessary to remove the iFix after it was installed follow these steps; they must be performed by a Synergy database administrator.

  1. Request that all users exit their Synergy sessions before you begin the uninstallation. Shutdown all Synergy databases using the ccmdb shutdown command. Verify that all users have exited with ccm monitor.

    > ccmdb shutdown <dbpath> # repeat per database
    > ccm monitor

  2. Stop the 7.1 Synergy services. This step must be performed by an admin user.

    Open the services dialog and stop the Synergy services. If you are unfamiliar with these services refer to the Synergy Administration Guide For Windows for additional details.

  3. Restore the original files replaced by 7.1.0.7 iFix003

    Before replacing the original files, remove the hidden attribute from files stored under the %CCM_HOME%\patches\7.1.0.7.003 directory and its subdirectories.

    Do this as user who has local admin rights.

    Use the attrib command to remove the Hidden attribute from
    the files. From a command prompt:

    > cd %CCM_HOME%\patches\7.1.0.7.003
    > attrib -h * /s /d

    The %CCM_HOME%\patches\7.1.0.7.003 directory contains two files and either three or four sub-directories.

    The two files are a README file and ccm_bp.ini. You do not need to be concerned with the ccm_bp.ini file.

    The three sub-directories that every installation will have are CCM_HOME, util, and WINSYS. If your installation contains the Synergy Database Administration Tools, there will be an additional sub-directory named database. This last directory is not hidden and the files it contains are not hidden.

    The util and WINSYS directories are empty, and can be ignored. The database directory may also be ignored at this time.

    The CCM_HOME directory contains a directory structure similar to that of your Synergy installation area. Any files that were removed or replaced from your installation area are under this directory.

    After removing the hidden attribute from all of the files stored under this CCM_HOME directory and its sub-directories, copy or move all of these files into the Synergy installation area directory structure, replacing the files that are currently there.

    For example, the file "ccmjava.jar" was replaced by this iFix.

    This file is located in the \lib directory. To replace the iFix version of the file with the original file, copy or move the previously saved "ccmjava.jar" file from the directory

    %CCM_HOME%\patches\7.1.0.7.003\CCM_HOME\lib

    to the directory

    %CCM_HOME%\lib

    Restore all CCM_HOME files replaced by this iFix. For a complete list of CCM_HOME files replaced, please see the above section titled, .

  4. Remove entries in patches.txt and patches.dat

    In the %CCM_HOME%\etc directory are files patches.txt and patches.dat. Using a text file editor (such as Notepad.exe), edit these files and remove the lines referencing this iFix.

    Save this file and exit the editor. If the resulting files are empty, then delete them.

  5. Remove the file %CCM_HOME%\etc\cli\xml\mode6.5\update_urls.xml from the run area if the run area is updated from 7.1.0.7.

  6. Remove 7.1.0.7.003 Key from the Registry

    On 32 bit systems this key is located at:

    HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\CM SYNERGY\7.1\Install\Patches\7.1.0.7.003.

    or

    HKEY_CURRENT_MACHINE\SOFTWARE\Telelogic\CM SYNERGY\7.1\Install\Patches\7.1.0.7.003.

    On 64 bit systems this key is located at:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Telelogic\CM SYNERGY\7.1\Install\Patches\7.1.0.7.003.

    Start the registry editor program by selecting Run... from the Start menu and typing regedit.exe in the Open text field.

    When the Registry Editor starts, browse to the appropriate key listed above. You will see a key labeled 7.1.0.7.003. Select this key by clicking on it with the mouse. Now delete the key by pressing Delete on your keyboard. Exit the registry editor.

  7. Reverse 7.1.0.7 iFix003 in databases

    If you have a customized model, using a model database, reinstate your previous model by performing a model install from your original customized model project to each database.

    If you used "ccmdb_patch_7107_003.bat" to install this iFix to your databases, the following three steps were performed when "ccmdb_patch_7107_003" was run:
    • Before the iFix was applied, affected database files were copied to <dbpath>\save\<filename>.p7107.003
    • The updated files from the iFix were copied to the database.
    • A line was appended to <database path>\db\MDL_INFO as a record of the iFix.

      To reverse these actions, perform the following steps for each patched database.
      1. Log in as "CM administrator" on the database server machine, and bring up a command window.

      2. Remove the database files that were changed:

        > del <dbpath>\lib\baselib.a

        Move the saved copy of the these files back into their original locations:

        > move <dbpath>\save\lib\baselib.a.p7107.003 <dbpath>\lib\baselib.a

        Repeat this step for each database file listed in .

      3. In the <database path>\db directory, there is a file named MDL_INFO. Using a text file editor (like Notepad.exe), edit this file and remove the lines referencing this iFix.

        Save this file and exit the editor.

        In the <database path>\etc directory is a file named patches.dat. Using a text file editor (like Notepad.exe), edit this file and remove the line referencing this iFix.

        Save this file and exit the editor. If the resulting files are empty, delete them.

  8. Restart the Synergy services

    Restart the services that were stopped in an step 2. Open the services dialog and start the Synergy services. If you are unfamiliar with these services refer to the Synergy Administration Guide For Windows for additional details.

  9. Unprotect the databases that were shut down in step 1

    > ccmdb unprotect <dbpath>

    Repeat for every database that was patched.

  10. Inform users to restart Synergy sessions.

Download package

The following sections provide detailed information related to this release.

Click the FC link below to obtain the release from Fix Central.


How critical is this fix?

Impact Assessment
Impact Description

This is a maintenance release. It contains fixes for client-reported and internally found defects.

Test Results

Definitions

Regression: An error in the Maintenance Delivery Vehicle (MDV) that produces incorrect or unexpected behavior causing a supported feature to stop functioning as designed.
This includes:

  • Coding errors that cause a regression
  • Documentation or packaging problems that cause a regression
  • Errors reported in a new function delivered in a MDV that cause a regression

Incomplete: An error in the MDV has not regressed, but does not work as designed.
This includes:

  • Fixed APARs which did not solve the original problem but did not break anything new
  • APARs reporting documentation errors, such as readme errors, that cause problems applying an MDV but do not lead to a regression

Notes:
  • Regression and incomplete APARs are considered fix-in-error or MDV-in-error
  • Definitions above apply only to valid APARs that result in product fixes (APARs returned as working-as-designed are not assessed for being fix-in-error)
  • Issues in major releases due to new functionality do not apply in this definition

There are no known regressions to report.

Problems solved

Defects resolved

Click the Fix List link in the table of contents above to review a list of the problems solved in this release.

Known side effects

Review the following list of known issues and open defects:

No known issues.

Open defects

Review the following list of open defects for Rational Synergy on the IBM Support Portal.

Review technote 1461170: Open APARs for Rational products available on the Web for information on how to configure your MyNotifications subscription account and subscribe to the APARs you are interested in following.

Change history

What's new

No new features or functions.

Click the link in the Download Options column:

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central (FC)?
Interim Fix 3 for 7.1.0.7 19 Jun 2014 English 1 FC

Technical support

Tab navigation


IBM Rational Software Support Communities

  • Visit the IBM Support Portal to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.

  • Visit developerWorks to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community.

  • Visit the Jazz Community if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track developement progress.

Helpful Hints For Obtaining Technical Assistance:

Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:

  • What software versions were you running when the problem occurred?
  • Do you have logs, traces, or messages that are related to the problem?
  • Can you reproduce the problem? If so, what steps do you take to reproduce it?
  • Is there a workaround for the problem? If so, be prepared to describe the workaround.

If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support.

Follow IBM Rational Client Support on Twitter | Facebook | YouTube | devWorks Blog


Problems (APARS) fixed
PI14062, PI16737, PI17937, PI17941, PM91004, PM96737, PM95186, PM96374, PM96372, PM96917, PM99216, PM99217, PM95030, PM96732, PM97599, PM96841, PM78412, PM78705, PM80393, PM80909, PM81838, PM83122, PM83848, PM84615, PM84943, PM85167, PM86555, PM88488, PM90743, PM75081, PM24260, PM29256, PM44981, PM58404, PM67614, PM70219, PM70252, PM71241, PM71913, PM72482, PM73138, PM73310, PM74669, PM74958, PM75814, PM76205, PM77071, PM77078, PM77872, PM78168, PM79427

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Rational Synergy
Installation

Software version:

7.1.0.7

Operating system(s):

AIX, Linux, Solaris, Windows

Reference #:

4037432

Modified date:

2014-06-19

Translate my page

Machine Translation

Content navigation