IBM(R) Rational(R) Synergy Fix Pack 7.1.0.5 ------------------------------------------- SUMMARY This README describes the contents of Synergy Fix Pack 7.1.0.5 and describes how to install the Fix Pack. 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 Fix Pack. SUPPORTED RELEASES This section lists the releases to which this Fix Pack may be applied. DELIVERABLE COMPONENTS AFFECTED This section lists the files that will be replaced by this Fix Pack. INSTALLATION INSTRUCTIONS This section describes how to apply the Fix Pack to your Synergy server and client installations and to your Synergy databases. REVERSING THE FIX PACK This section describes how to remove the Fix Pack. CONTACTING SUPPORT If you need assistance or have any problems with this Fix Pack, contact Synergy Support as described at the very end of this README. PROBLEMS Synergy Fix Pack 7.l.0.5 fixes the following problems: R#40967 Improve performance while retrieving tasks info for a project grouping R#41073 Improve performance while doing the Project and PG Update from Java Client. R#41095 Runtime exception in session manager R#41101 Improve session start up performance R#41170 Do not sync static relative subprojects from prep projects R#41180 Highlighting of object in the History view R#41241 Workspace syncing fails when subproject is maintained using the Unix client on Windows. R#41345 NullPointerException thrown when History dialog is kept open and file is renamed. R#41363 Could not rotate log files R#41479 Add timeout to Synergy server R#41617 Update JREs to fix a security issue. R#41676 Change workarea to use Synergy 8-bit encoding as default encoding to avoid data lost for source files R#41695 Project grouping based on release component R#41697 Project specific Patterns to Ignore R#41718 When the server starts new backend sessions, there is a chance that it may lock out access to that database R#41735 Improve server resource monitoring R#41736 Change Synergy GUI to allow empty string for the Server field in login dialog R#41770 CM72, CM71: When RDS was down, and user performs any Synergy operations, it reports 'Invalid username of password' error. R#41844 Add line separator to API dump results PM36372 R#40216 Work-Area path is sometimes not displayed in project properties pane PM42319 R#40792 Fix ccm fs_check regression introduced between 7.1 and 7.1.0.1 PM46360 R#41173 Opening a static file in a static project can display incorrect file contents under specific conditions. PM46403 R#41179 Task Release of project not refreshed when Release is modified PM46612 R#41201 Project work area not updated in web mode when release changed and subdirectory template includes %release PM46629 R#41203 "Change Type" Fails almost silently due to multiple project versions Request to be fixed in 7.1 Synergy PM46775 R#41212 Patch Request: R#40781 - Group Security does not refresh PM48697 R#41433 Asynchronous archiver needs to clean up *.new archive files when it starts up. PM48698 R#41432 archive_fix needs to handle the case where the object or its siblings are not archived yet. PM48893 R#41462 Get File Path Sync Failed!!! error when opening file in Web-Mode client PM49376 R#41536 patch request for the problem: "cannot authenticate users in eclipse with web mode on linux with Synergy 7.1" PM49632 R#41542 Apparent memory leak in Synergy Properties dialog PM49687 R#41675 bad DUMPDIR BAR_ACT_LOG BAR_DEBUG_LOG values in ONCONFIG file PM49847 R#41569 Java client sometimes hangs during sync and delete operations PM50024 R#41606 ccm_platform script resulting in "unrecognized host architecture" on supported platform PM50599 R#41687 0x00 character placed after the 2048 first bytes is not detected + range_for_keyword_expand setting not used PM50786 R#41722 Modify a project and subprojects' versions does not modify the subprojects links PM50825 R#41731 No warning for version length on Baseline creation PM51108 R#41759 Synergy-OSLC error when source has no cache file: "Status 404 No Content exists for resource..." PM51284 R#41778 .ccmwaid.inf of subproject not updated after changing the version and ccm project problem PM51601 R#41820 Closing PG Properties window during Refresh throws URE PM51768 R#41841 project view not refreshed after update This Fix Pack includes the following fixes from Synergy 7.1.0.4 iFix002: PM47124 R#41249 IO and encoding errors during a sync when files are being read. PM47283 R#41271 Copy to file system feature is truncating some files with Web mode. PM44572 R#41241 Workspace syncing fails when subproject is maintained using the Unix client on Windows. SUPPORTED RELEASES This Fix Pack may only be applied to Synergy Release 7.1 with Fix Pack 7.1.0.1 already installed. It may also be applied on top of Fix Packs 7.1.0.2, 7.1.0.3, or 7.1.0.4. This Fix Pack is cumulative, and rolls in all fixes from Fix Packs 7.1.0.2, 7.1.0.3 and 7.1.0.4 as well as the fixes from 7.1.0.4 iFix002. It does not include fixes from Fix Pack 7.1.0.1. WHO SHOULD APPLY THIS FIX PACK This Fix Pack should be installed at all sites running Synergy Release 7.1. WHERE TO APPLY THIS FIX PACK This Fix Pack should be installed to all Synergy installations (CCM_HOME) and clients. This Fix Pack 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. DELIVERABLE SYNERGY COMPONENTS AFFECTED Those marked with (*) have changed since the last Fix Pack, 7.1.0.4. Database files affected by the Fix Pack: Database_path\etc\mime_cvtype_mappings.properties Database_path\lib\apilib.a (*) Database_path\lib\baselib.a (*) Database_path\lib\csetlib.a Database_path\lib\dcmlib.a Database_path\lib\focilib.a Database_path\lib\grpsclib.a Database_path\lib\mflib.a Database_path\lib\notify.a Database_path\lib\ptlib.a Database_path\lib\rmlib.a Database_path\lib\soadf.a Database_path\lib\typedef.a CCM_HOME files affected by the Fix Pack: %CCM_HOME%\bin\ccm.exe (*) %CCM_HOME%\bin\ccmdb.exe %CCM_HOME%\bin\ccmsrv.exe (*) %CCM_HOME%\bin\ccm_aci.exe %CCM_HOME%\bin\ccm_win.exe %CCM_HOME%\bin\CMWinUtils.dll (*) %CCM_HOME%\bin\dbutil\ccmdb_load_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\bsdtar.exe %CCM_HOME%\bin\util\ccm_ci.exe %CCM_HOME%\bin\util\ccm_eng_inf.exe %CCM_HOME%\bin\util\ccm_ess.exe %CCM_HOME%\bin\util\ccm_gui.exe %CCM_HOME%\bin\util\ccm_objreg.exe %CCM_HOME%\bin\util\ccm_router.exe %CCM_HOME%\bin\util\ccm_websrv.exe %CCM_HOME%\etc\ccm_resource.properties (*) %CCM_HOME%\etc\ccm.properties %CCM_HOME%\etc\CcmError.properties (*) %CCM_HOME%\jetty\lib\commons-logging-api.jar %CCM_HOME%\jetty\lib\JSON4J.jar %CCM_HOME%\jetty\webapps\jsp\dump.jsp (*) %CCM_HOME%\jetty\webapps\jsp\resource_monitor.jsp (*) %CCM_HOME%\jetty\webapps\jsp\server_diagnosis.jsp (*) %CCM_HOME%\jetty\webapps\WEB-INF\web.xml (*) %CCM_HOME%\jre\* (*) %CCM_HOME%\lib\adminlib.a %CCM_HOME%\lib\ccmjava.jar (*) %CCM_HOME%\lib\ccmlib.a (*) %CCM_HOME%\lib\ccm_api.lib %CCM_HOME%\lib\ccm_make.a %CCM_HOME%\lib\cilib.a %CCM_HOME%\lib\cslib.a %CCM_HOME%\lib\c_ccmlib.a %CCM_HOME%\lib\eislib.a (*) %CCM_HOME%\lib\guilib.a %CCM_HOME%\lib\icu4j.jar %CCM_HOME%\lib\libAPIac.a %CCM_HOME%\lib\objreglib.a %CCM_HOME%\lib\rfclib.a %CCM_HOME%\lib\sa_englib.a %CCM_HOME%\lib\sa_mdlinst.a %CCM_HOME%\lib\tdscommonlib.jar %CCM_HOME%\lib\tdscryptolib.jar %CCM_HOME%\lib\tdsjndilib.jar %CCM_HOME%\lib\tdsloggerlib.jar %CCM_HOME%\lib\uislib.a (*) %CCM_HOME%\lib\upgrade.a %CCM_HOME%\packfiles\base.cpk (*) %CCM_HOME%\packfiles\base.model (*) %CCM_HOME%\packfiles\training.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 Fix Pack into Synergy databases. This Fix Pack contains modifications to the software that must be installed in the installation directory (CCM_HOME changes). This Fix Pack also contains changes that must be installed in Synergy databases (model changes). Once you have installed 7.1.0.5, you should not install any individual iFix that does not clearly state that it may be installed on top of 7.1.0.5, 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 # Repeat per database > ccm monitor 2. To apply the Fix Pack 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 Fix Pack; the network installation itself must be updated once. 3. Once you have logged in as the appropriate user, run the Fix Pack executable, 7.1-RATL-RATISYNE-Windows-FP0.5.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 Fix Pack. 4. Patch standard databases. If you do not have a customized model, you should apply this Fix Pack to each of your databases. ALL databases must be patched prior to use with this Fix Pack. 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:\ccm71 # Adjust as appropriate > set PATH=%CCM_HOME%\bin;%PATH% > ccmdb unprotect > ccmdb_patch_7105 > postdb_7105.bat 5. Inform users that they can restart their Synergy sessions. This Fix Pack contains a Windows client component. Users of Synergy Windows GUI will be prompted to download the Fix Pack 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://:/client/Update_7.1-0.5.exe. Alternatively, the executable, Update_7.1-0.5.exe, can be distributed to Windows CLI and Windows Synergy Classic client users, so they can execute it directly, to update their client installations. POST INSTALLATION INSTRUCTIONS The following apply if you have not previously installed Fix Pack 7.1.0.4. 1. This Fix Pack includes Synergy support for Red Hat Linux 6.0. Customers who want to run Synergy on Red Hat 6.0 must first install the 32-bit RPM package. Red Hat provides documentation on how to do this. 2. The fix for PM43781 R#40932 changes the behavior in traditional mode to be consistent with web mode, so that keyword values may not span more than a single line. Note that this is a change in behavior. The following apply if you have not previously installed Fix Pack 7.1.0.2. 1. As part of the fix for R#35386, DCM event logging now uses a router-based semaphore for mutex. A new model attribute is supported: dcm_event_log_semaphore_timeout: An integer attribute on the model object that overrides the factory default of 60 seconds for the DCM event log semaphore timeout. The value of this attribute is an integer that represents the timeout in seconds. If DCM operations report a semaphore timeout, this timeout can now be adjusted. 2. The fix for R#35100 applies to work areas in web mode only. With this fix, it is possible to ignore files in a subdirectory, based on a pattern. Note that the backslash character (\) needs to be doubled (\\) if it appears in a pattern. The forward slash (/) does not need to be doubled. 3. The fix for R#35146 fixes both "ccmdb upgrade -w" and win_fixup, so that they do not do newline translation for Mac newlines (i.e., a carriage return without a newline will now be left as is). Although this Fix Pack does not require a database upgrade, users on a release older than 7.1.0.1 will need to first upgrade to 7.1.0.1, which does not include this fix. Therefore, such users who have files with Mac newlines will need to upgrade to 7.1.0.1 without using the "-w" option. After applying this Fix Pack, they can then run win_fixup, which includes this fix. Note that this only applies to a small group of users, who are moving a database from Windows to UNIX (or the converse), and upgrading from pre-7.1.0.1, and have Mac newlines in their source files. 4. R#35310 manifested itself with the behavior that modifiable projects were showing up in a gray font, in the Synergy GUI. The problem was a bad base.cpk file delivered with Fix Pack 7.1.0.1, and only affected customers who created a new database from this packfile. Customers who created a new database from the base.cpk packfile delivered with Fix Pack 7.1.0.1 will need to check their database and possibly run the ccmdb repair command to fix it. After applying this Fix Pack, customers should run the ccmdb check command to check all their databases. If ccmdb check command reports errors such as this: Missing acc key for attribute member_status. Missing acc key for attribute created_in. Missing acc key for attribute local_to. Missing acc key for attribute modifiable_in. Missing acc key for attribute platform. Missing acc key for attribute completed_in. Missing acc key for attribute crstatus. Missing acc key for attribute automatic_task_key. Missing acc key for attribute case_preserved_name. then the following command needs to be run on each such database: ccmdb repair -t acckeys 5. The fix for PM49687 is for new Informix databases servers created by "ccmsrv create" after installing this Fix Pack. If you have previously created a database server on Windows, and the file %CCM_HOME%\informix\etc\ONCONFIG contains the following lines: DUMPDIR $INFORMIXDIR mp BAR_ACT_LOG $INFORMIXDIR mpar_act.log BAR_DEBUG_LOG $INFORMIXDIR mpar_dbug.log then you can correct these lines manually, as follows. Steps: 1. Shut down all databases. 2. Shut down the database server with "ccmsrv offline" 3. Edit %CCM_HOME%\informix\etc\ONCONFIG to change the above lines to: DUMPDIR $INFORMIXDIR\tmp BAR_ACT_LOG $INFORMIXDIR\tmp\bar_act.log BAR_DEBUG_LOG $INFORMIXDIR\tmp\bar_dbug.log 4. Bring the database server online with "ccmsrv online" 5. Unprotect all the databases. Note that Synergy does not use the ON-Bar feature, so the bad values for BAR_ACT_LOG and BAR_DEBUG_LOG will not matter. Also note that when Informix sees a bad value for DUMPDIR, it will default to $INFORMIXDIR\tmp, so the bad value for DUMPDIR will not matter either. Therefore, this step of correcting the ONCONFIG file is optional. REVERSING THE FIX PACK (WINDOWS) If it is necessary to remove the Fix Pack 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 # 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.5 Before replacing the original files, you must remove the hidden attribute from files stored under the %CCM_HOME%\patches\7.1.0.5 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.1.0.5 > attrib -h * /s /d The %CCM_HOME%\patches\7.1.0.5 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 Fix Pack. This file is located in the \lib directory. To replace the Fix Pack 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.5\CCM_HOME\lib to the directory %CCM_HOME%\lib. Restore all CCM_HOME files replaced by this Fix Pack. 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 Fix Pack. Save this file and exit the editor. If the resulting files are empty, then they should be deleted. 5. Remove 7.1.0.5 Key from the Registry You must remove the 7.1.0.5 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.5. or HKEY_CURRENT_MACHINE\SOFTWARE\Telelogic\CM SYNERGY\7.1\Install\Patches\7.1.0.5. On 64 bit systems this key is located at: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Telelogic\CM SYNERGY\7.1\Install\Patches\7.1.0.5. 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.1.0.5. 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 Fix Pack 7.1.0.5 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_7105.bat" to install Fix Pack 7.1.0.5 to your databases, the following three steps were performed when "ccmdb_patch_7105" was run: * Before the Fix Pack was applied, affected database files were copied to \save\.p7105 * The updated files from the Fix Pack were copied to the database. * A line was appended to \db\MDL_INFO as a record of the Fix Pack. 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 \lib\baselib.a Move the saved copy of the these files back into their original locations: > move \save\baselib.a.p7105 \lib\baselib.a Repeat this step for each database file listed in DELIVERABLE SYNERGY COMPONENTS AFFECTED 6.3. In the \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 Fix Pack. Save this file and exit the editor. In the \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 Fix Pack. 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 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 Fix Pack, contact Synergy Support. Synergy Support information is available at: http://www.ibm.com/software/rational/support/telelogic (C) Copyright IBM Corporation 2009, 2011 U.S. Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.