IBM(R) Rational(R) Synergy iFix 7.1a.04
---------------------------------------

SUMMARY

This README describes the contents of Synergy iFix 7.1a.04
and describes how to install the iFix. This README may be revised 
and reissued at a later date. To ensure you have the latest version of this
README, check the patch page on the Synergy Support Web site. The README has
the following sections:

    PROBLEMS
      This section describes the problems fixed in this iFix.

    SUPPORTED RELEASES
      This section lists the releases to which this iFix may
      be applied.

    DELIVERABLE COMPONENTS AFFECTED
      This section lists the files that will be replaced by
      this iFix.

    INSTALLATION INSTRUCTIONS
      This section describes how to apply the iFix to your
      Synergy server and client installations and to your
      Synergy databases.

    POST INSTALLATION INSTRUCTIONS
      This optional section describes any steps that should be taken after
      installing this iFix.  

    REVERSING THE IFIX
      This section describes how to remove the iFix.

    CONTACTING SUPPORT
      If you need assistance or have any problems with this
      iFix, contact Synergy Support as described at the
      very end of this README.

PROBLEMS

iFix 7.1a.04 to Synergy Release 7.1a fixes the following problems:

 1) R#37956 PM23269 In CLI, no msg to notify merge parallel objects
                    before check in
 2) R#38211 PM24591 Synergy Web Server needs to be restarted to allow users
                    log in using Web Mode for 7.1a 
 3) R#38714 PM27321 Cannot reconcile work area in link based wa on shared
                    project in Synergy web CLI

iFix 7.1a.04 to Synergy Release 7.1a includes iFix 7.1a.03,
which fixes the following problem:

 1) R#37293 PM12938 Wrong file name appears when open a file in history

iFix 7.1a.04 to Synergy Release 7.1a includes iFix 7.1a.02,
which fixes the following problem:

 1) R#37145 PM10794 Unable to start a java cli/ JC(http) session,
                    if the user is added thro ugh Change 

iFix 7.1a.04 to Synergy Release 7.1a includes iFix 7.1a.01,
which fixes the following problems:

 1) R#34498 <none>  Dates are sorted alphabetically instead of by date
                    in the GUI
 2) R#34854 PM03064 URE when showing project's history after creating
                    a baseline
 3) R#35494 PM07284 _archive_info attribute missing from object versions DCM
                    received in Synergy 7.1.0.1
 4) R#35495 PM07306 multiple operations hitting the same cache file at the
                    same time corrupts it
 5) R#35496 <none>  Add more log information on session allocation error in
                    asynchronous archive
 6) R#35686 PM04924 files truncated when copied in the workarea in Web Mode
 7) R#35687 PM05634 WA population problem with nested static subprojects
 8) R#35689 PM06754 Copy project disregards translate ascii setting when
                    writing static work areas to Windows.
 9) R#35690 PM07021 Change state of an object to test with the web-client
10) R#35691 PM08045 Read security is broken in web mode
11) R#35692 <none>  JC After copyproject from static subproject, workarea does
                    not show the static files under its root directory
12) R#35694 <none>  Relative work area directory not cleaned up when
                    subproject is replaced with one with absolute work area
13) R#35706 PM02629 ascii files containing character 0d are corrupted by the
                    sync in web mode
14) R#35708 <none>  In HTTP mode after DCM receive, sync does
                    not create links to sub-projects under top-project
15) R#35709 PM01432 Changing RDS password does not require old password
16) R#35710 PM05209 Users are not getting authenticated (as expected) to login
                    to Synergy client (Web Mode) via RDS 5.0.
17) R#35721 PK99813 Project checkout with w/o subprojects and update turned on
                    binds new static subprojects
18) R#35722 <none>  Creation of prep project does not set the root dir to
                    group writable in new wa.
19) R#35724 PM01665 Network errors cause intermittent ACcent aborts aborts
                    in Synergy client using http mode
20) R#35739 <none>  ccm_eng_inf.exe is terminated when logging on Windows as
                    Administrator after reboot.
21) R#35744 <none>  DCM receive can overwrite copy of folder template,
                    process rule, process or release with older data
22) R#35745 <none>  ccm reconcile is failing with object not a member error
                    in Java CLI.
23) R#35762 <none>  In HTTP mode, 'ccm dcm -s -el -index N -messages/-info'
                    does not show correct details.
24) R#35777 <none>  The value _archive_info of a 4.8GB file object remains
                    none.
25) R#35778 PM09593 Symlink object source is lost after checking out the
                    object
26) R#35783 <none>  "ccm cr_summary" commands gives innacurate size of
                     attachments
27) R#35789 <none>  Process rules of the process are getting set to an empty
                    set even though they are not modified.
28) R#35791 <none>  In Synergy CLI, relate/unrelate fail if owner is static,
                    even in ccm_admin role
29) R#35794 <none>  Synergy/CRAPI should support Set-Cookie headers; work with
                    load balancers
30) R#35796 <none>  After central CR migrate, some ghost CRs don't have
                    is_ghost_problem attribute
31) R#35797 <none>  Change's Synergy sessions reload ccm users data twice when
                    the Perl API RefreshUsers is called. 
32) R#35798 <none>  Java CLI throws Socket Exception upon setting the workarea
                    of the project.
33) R#35799 <none>  General IO error after stopping a Copy Project operation
34) R#35800 <none>  ccm merge on a file with spaces in the name can delete
                    other files in the work area
35) R#36409 <none>  Archiving fails when server is restarted while archiving
                    a large object

SUPPORTED RELEASES

  This iFix may only be applied to Synergy Release 7.1a.
  It may also be applied on top of interim fixes 7.1a.01, 7.1a.02, and
  7.1a.03.

WHO SHOULD APPLY THIS IFIX

  This iFix should be installed at all sites running Synergy Release 7.1a.

WHERE TO APPLY THIS IFIX

  This iFix should be installed to all Synergy installations (CCM_HOME) and
  clients. This iFix should first be installed to the machine where the
  Synergy router daemon is running followed by installation to other server
  machines and finally deployed to client machines.  This iFix must also be
  applied to each Synergy 7.1a database.

DELIVERABLE SYNERGY COMPONENTS AFFECTED

  Database files affected by the iFix:

  Database_path\lib\apilib.a
  Database_path\lib\baselib.a
  Database_path\lib\dcmlib.a
  Database_path\lib\focilib.a
  Database_path\lib\ptlib.a

  CCM_HOME files affected by the iFix:

  %CCM_HOME%\lib\ccmjava.jar
  %CCM_HOME%\lib\cslib.a
  %CCM_HOME%\lib\tdscommonlib.jar
  %CCM_HOME%\lib\tdscryptolib.jar
  %CCM_HOME%\lib\tdsjndilib.jar
  %CCM_HOME%\lib\tdsloggerlib.jar
  %CCM_HOME%\bin\ccmdb.exe
  %CCM_HOME%\bin\dbutil\ccmdb_clear_binvals.exe
  %CCM_HOME%\bin\dbutil\ccmdb_dbsinfo_inf.exe
  %CCM_HOME%\bin\dbutil\ccmdb_dump_inf.exe
  %CCM_HOME%\bin\dbutil\ccmdb_index_inf.exe
  %CCM_HOME%\bin\dbutil\ccmdb_load_inf.exe
  %CCM_HOME%\bin\dbutil\ccmdb_lock_inf.exe
  %CCM_HOME%\bin\dbutil\ccmdb_mkdbs_inf.exe
  %CCM_HOME%\bin\dbutil\ccmdb_names_inf.exe
  %CCM_HOME%\bin\dbutil\ccmdb_refchk_inf.exe
  %CCM_HOME%\bin\dbutil\ccmdb_serverinfo_inf.exe
  %CCM_HOME%\bin\dbutil\ccmdb_table_inf.exe
  %CCM_HOME%\bin\dbutil\ccmdb_update.exe
  %CCM_HOME%\bin\util\ccm_eng_inf.exe

  WARNING:
    This iFix must be reapplied to any new databases you create by 
    unpacking base.cpk.

INSTALLATION INSTRUCTIONS (WINDOWS)

  Before you begin, make sure that you have performed a successful backup of
  your Synergy databases and Installation areas.  These backups are the only
  supported means of reversing the installation of this iFix into
  Synergy databases.

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

  This iFix also contains changes that must be installed in Synergy
  databases (model changes).

  Once you have installed iFix 7.1a.04, you should not install
  any individual iFix that does not clearly state that it may be
  installed on top of iFix 7.1a.04, 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. 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.  Users of existing network
     installations should not install the iFix; the network
     installation itself must be updated once.

  3. Once you have logged in as the appropriate user, run the iFix
     executable, 7.1a-RATL-RATISYNE-Windows-IF.04.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.

  4.  Patch standard databases.

     If you do not have a customized model, you should 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, you
     should 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:\ccm71a         # Adjust as appropriate
      > set PATH=%CCM_HOME%\bin;%PATH%
      > ccmdb unprotect <dbpath>
      > ccmdb_patch_71a-04 <dbpath>
      > postdb_71a_04.bat <dbpath> <host> <admin_user> <admin_user_password>

  5. Inform users that they can restart their Synergy sessions.

     This iFix contains a Windows client component. Users of
     Synergy Windows GUI will be prompted to download the
     iFix when they start a session. Users of Windows CLI and Windows
     Synergy Classic clients should be requested to patch their
     clients by browsing to:
     http://<helpserver>:<port#>/client/Update_7.1a.04.exe.

     Alternatively, the executable, Update_7.1a.04.exe, can be distributed
     to Windows CLI and Windows Synergy Classic client users, so they
     can execute it directly, to update their client installations.




REVERSING THE IFIX (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.1a 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 iFix 7.1a.04

     Before replacing the original files, you must remove the
     hidden attribute from files stored under the
     %CCM_HOME%\patches\7.1a.04 directory and its subdirectories
     This must as run by a user that 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.1a.04
       > attrib -h * /s /d

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

     The two files are this 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.1a.04\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: DELIVERABLE SYNERGY COMPONENTS AFFECTED.

  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 (like 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 they should be deleted.

  5. Remove 7.1a.04 Key from the Registry

     You must remove the 7.1a.04 key from the registry.

     On 32 bit systems this key is located at:

       HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\CM SYNERGY\7.1a\Install\Patches\7.1a.04.

    or

       HKEY_CURRENT_MACHINE\SOFTWARE\Telelogic\CM SYNERGY\7.1a\Install\Patches\7.1a.04.

     On 64 bit systems this key is located at:

       HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Telelogic\CM SYNERGY\7.1a\Install\Patches\7.1a.04.

     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 should see a key labeled 7.1a.04. Select this key by
     clicking on it with the mouse.  Now delete the key by pressing Delete
     on your keyboard.  Exit the registry editor.

  6.  Reversing iFix 7.1a.04 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_71a-04.bat" to install iFix 7.1a.04
      to your databases, the following three steps were performed
      when "ccmdb_patch_71a-04" was run:

      *  Before the iFix was applied, affected database files were
         copied to <dbpath>\save\<path>.p71a04

      *  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.

      6.1. Log in as "CM administrator" on the database server machine, and
           bring up a command window.

      6.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.p71a04 <dbpath>\lib\baselib.a

           Repeat this step for each database file listed in
           DELIVERABLE SYNERGY COMPONENTS AFFECTED

      6.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, then they should be deleted.

  7.  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.

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

       > ccmdb unprotect <dbpath>

      Repeat for every database that was patched.

  9. Inform users that they can restart their Synergy sessions.

CONTACTING SUPPORT

  If you need assistance or have any problems with this iFix, contact
  Synergy Support.

  Synergy Support information is available at:

   http://www.ibm.com/software/rational/support/telelogic

(C) Copyright IBM Corporation 2009, 2010
U.S. Government Users Restricted Rights - Use, duplication, or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.

