# Rational Synergy Fix Pack 6 (7.1.0.6) for 7.1

## Abstract

IBM Rational Synergy Fix Pack 7.1.0.6 has been made generally available and contains fixes to version 7.1 including all predecessor fix packs.

Sections Description
This section provides an overview on what is new in this release whith a description of any new functionality or enhancements when applicable.
This section provides information related to the impact of this release to allow you to assess how your environment may be affected.
This section provides important information to review prior to the installation of this release.
This section provides the installation instructions necessary to apply this release into your environment.
This section contains a link to the known problems (open defects) identified at the time of this release.
Supporting Documentation
Document Description
Click the link to navigate to the system requirement report page. To run the report, select your Product, Version and Operating System.
Note: Choose the parent version of your product to see the system requirements for fix pack releases.
Click to browse for the version of your product information center available on the product information library page.
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.

## Installation Instructions

Where to Apply this Fix Pack

Apply this Fix Pack 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.5 iFix001.

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/focilb.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  * Database_path/lib/Unix/migrate.rul  * Database_path/lib/Windows/migrate.rul

CCM_HOME files affected by the Fix Pack:

All Platforms

CCM_HOME/etc/ccm.properties
CCM_HOME/etc/ccm_resource.properties
*
CCM_HOME/etc/CcmError.properties

*
CCM_HOME/jetty/*

*
CCM_HOME/jre/*

CCM_HOME/lib/c_ccmlib.a

CCM_HOME/lib/ccm_make.a
*
CCM_HOME/lib/ccmjava.jar
*
CCM_HOME/lib/ccmlib.a
*
CCM_HOME/lib/cilib.a

CCM_HOME/lib/cslib.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/packfiles/base.cpk
*
CCM_HOME/packfiles/base.model
*
CCM_HOME/packfiles/training.cpk

UNIX

  * CCM_HOME/bin/ccm
*
CCM_HOME/bin/ccm_aci
*
CCM_HOME/bin/ccm_install

CCM_HOME/bin/ccm_patch
*
CCM_HOME/bin/ccm_server

CCM_HOME/bin/ccmdb

CCM_HOME/bin/ccmdb_ora                       (Oracle)

CCM_HOME/bin/ccmsrv

CCM_HOME/bin/dbutil/ccmdb_info_inf           (Informix)

CCM_HOME/bin/dbutil/ccmdb_info_ora           (Oracle)

CCM_HOME/bin/dbutil/ccmdb_refchk_inf         (Informix)

CCM_HOME/bin/dbutil/ccmdb_refchk_ora         (Oracle)

CCM_HOME/bin/dbutil/ccmdb_serverinfo_inf     (Informix)

CCM_HOME/bin/dbutil/ccmdb_table_inf          (Informix)

CCM_HOME/bin/dbutil/ccmdb_table_ora          (Oracle)

CCM_HOME/bin/dbutil/ccmdb_update             (Informix)

CCM_HOME/bin/dbutil/ccmdb_update_ora         (Oracle)

CCM_HOME/bin/dbutil/ccmsrv_create

CCM_HOME/bin/dbutil/ccmsrv_util

*
CCM_HOME/bin/util/ccm_ci
*
CCM_HOME/bin/util/ccm_eng_inf                (Informix)
*
CCM_HOME/bin/util/ccm_eng_ora                (Oracle)
*
CCM_HOME/bin/util/ccm_gui

CCM_HOME/bin/util/ccm_platform

CCM_HOME/bin/util/ccmesd
*
CCM_HOME/bin/util/jetty_for_ccm

CCM_HOME/informix/*

CCM_HOME/lib/ccm_api.a
*
CCM_HOME/lib/ccm_files

CCM_HOME/lib/informix_files
*
CCM_HOME/lib/jre_files

Microsoft Windows
  * CCM_HOME\bin\ccm.exe
*
CCM_HOME\bin\ccm_aci.exe

CCM_HOME\bin\ccm_win.exe

CCM_HOME\bin\ccmdb.exe

CCM_HOME\bin\ccmsrv.exe

CCM_HOME\bin\CMWinUtils.dll

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\lib\ccm_api.lib

Installation Instructions (UNIX)

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 Fix Pack 7.1.0.6, do not install any individual iFix or Fix Pack that does not clearly state that it may be installed on top of Fix Pack 7.1.0.6, unless informed otherwise by Synergy Support.

1. To install this Fix Pack on UNIX, use the ccm_patch script. If you do not have the ccm_patch script, please 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. Shut down the Informix database server.
This step needs to be performed only for Linux and Solaris installations that use an Informix database, and have not already installed Interim Fix 7.1.0.3 iFix001 or Fix Pack 7.1.0.4 or Fix Pack 7.1.0.5 (i.e., if you are upgrading directly from 7.1.0.1 or 7.1.0.2 or 7.1.0.3 to 7.1.0.6).
 $su - informix informix$ CCM_HOME=/usr/local/ccm71 # Adjust as appropriate informix$PATH=$CCM_HOME/bin:$PATH informix$ export CCM_HOME PATH informix$ccmsrv offline [-s servername] # Repeat per db server  6. Update the Synergy installation directory. Use the ccm_patch command. The argument to ccm_patch is the full path to the Fix Pack 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
Use the tar file that is appropriate for your UNIX platform.

For AIX:
 # ccm_patch <PATH>/7.1-RATL-RATISYNE-AIX-FP0.6.tar.gz
For Linux:
 # ccm_patch <PATH>/7.1-RATL-RATISYNE-Linux-FP0.6.tar.gz
For Solaris:
 # ccm_patch <PATH>/7.1-RATL-RATISYNE-Solaris-FP0.6.tar.gz # exit

Repeat this command for each installation directory.

Once the installation directory has been updated the Synergy daemons should be restarted by the ccm_root user.
 ccm_root$ccm_start_daemons  7. Restart the Informix database server. This step needs to be performed only for Linux and Solaris installations that use an Informix database, and have not already installed Interim Fix 7.1.0.3 iFix001 or Fix Pack 7.1.0.4 or Fix Pack 7.1.0.5 (i.e., if you are upgrading directly from 7.1.0.1 or 7.1.0.2 or 7.1.0.3 to 7.1.0.6). $ su - informix informix$CCM_HOME=/usr/local/ccm71 # Adjust as appropriate informix$ PATH=$CCM_HOME/bin:$PATH informix$export CCM_HOME PATH informix$ ccmsrv online [-s servername] # Repeat per db server
8. Use the ccm_patch command to apply this Fix Pack to one or more databases.

If you have a customized model using a custom model database, you should 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.6 <dbpath>  9. 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://<helpserver>:<port#>/client/Update_7.1-0.6.exe  Alternatively, the executable, Update_7.1-0.6.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 (UNIX) 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 <database_path>  Reversing the Fix Pack (UNIX) If it is necessary to remove the Fix Pack after it was installed, follow these steps. If you have a Windows client, see Reversing the Fix Pack (Microsoft Windows). Before you begin, make sure that you have performed a successful backup of your Synergy databases and installation areas. NOTE: If you need to reverse the Fix Pack on Linux or Solaris with Informix, and you have installed this Fix Pack directly on top of 7.1.0.1 or 7.1.0.2 or 7.1.0.3, without installing 7.1.0.3 iFix 001 or 7.1.0.4 or 7.1.0.5, then your databases will need to be backed up and deleted before you reverse this Fix Pack, and your Informix server will then need to be deleted. Once you have restored the patched files, you need to recreate the Informix server. You will then need to unpack your databases. Please contact Synergy Support for assistance in reversing this Fix Pack. 1. In preparation for the following steps, ask all users to exit their Synergy sessions. As 'ccm_root', shut down all Synergy databases that were patched with Fix Pack 7.1.0.6. 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. Steps 2 to 4 need to be performed ONLY for Linux and Solaris installations that have an Informix database server and installed this Fix Pack directly on top of 7.1.0.1 or 7.1.0.2 or 7.1.0.3, without installing 7.1.0.3 iFix 001 or 7.1.0.4 or 7.1.0.5. Otherwise, skip to step 5.

Delete all databases
 ccm_root$ccmdb delete <dbpath> # Repeat per database  3. This step needs to be performed ONLY for Linux and Solaris installations that have an Informix database server and installed this Fix Pack directly on top of 7.1.0.1 or 7.1.0.2 or 7.1.0.3, without installing 7.1.0.3 iFix 001 or 7.1.0.4 or 7.1.0.5. Otherwise, skip to step 5. Shut down the Informix database server. $ su - informix informix$CCM_HOME=/usr/local/ccm71 # Adjust as appropriate informix$ PATH=$CCM_HOME/bin:$PATH informix$export CCM_HOME PATH informix$ ccmsrv offline [-s servername] # Repeat per db server
4. This step needs to be performed ONLY for Linux and Solaris installations that have an Informix database server and installed this Fix Pack directly on top of 7.1.0.1 or 7.1.0.2 or 7.1.0.3, without installing 7.1.0.3 iFix 001 or 7.1.0.4 or 7.1.0.5. Otherwise, skip to step 5.

Delete the Informix database server.

NOTE: Before you delete an Informix Server, please print and save the server information so you can use the same parameters to recreate this Informix server later.
 informix$ccmsrv status -all [-s servername] > servername.info # Repeat per db server informix$ ccmsrv delete -y [-s servername] # Repeat per db server
5. Remove the following files from the directory $CCM_HOME/jetty/lib if they exist  jetty-deploy-8.1.3.v20120416.jar jetty-http-8.1.3.v20120416.jar jetty-io-8.1.3.v20120416.jar jetty-security-8.1.3.v20120416.jar jetty-server-8.1.3.v20120416.jar jetty-servlet-8.1.3.v20120416.jar jetty-servlets-8.1.3.v20120416.jar jetty-util-8.1.3.v20120416.jar jetty-webapp-8.1.3.v20120416.jar jetty-xml-8.1.3.v20120416.jar servlet-api-3.0.jar slf4j-api-1.6.4.jar slf4j-jdk14-1.6.4.jar  Also remove the following directories from$CCM_HOME/jetty/lib if they exist
 jndi jsp jta monitor policy spdy annotations ext
6. Restore the installation files from before Fix Pack 7.1.0.6

$CCM_HOME contains a save directory structure that contains all files that were removed or replaced during the Fix Pack installation process. The files are saved with a suffix of _p7.1.0.6. 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 Fix Pack should be replaced. 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 Fix Pack: $ 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 -p $CCM_HOME/save/lib/ccmjava.jar_p7.1.0.6 \$CCM_HOME/lib/ccmjava.jar
Repeat this step for each $CCM_HOME file listed in Deliverable Synergy Components Affected. 7. 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 Fix Pack.

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

8. 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
9. Steps 9 and 10 need to be performed ONLY for Linux and Solaris installations that have an Informix database server and installed this Fix Pack directly on top of 7.1.0.1 or 7.1.0.2 or 7.1.0.3, without installing 7.1.0.3 iFix 001 or 7.1.0.4 or 7.1.0.5. Otherwise, skip to step 11.

Recreate the Informix database server(s) deleted in Step 4, using the database server information previously saved (i.e. rootdbs, logs, temp, ccm).
 $su - informix informix$ CCM_HOME=/usr/local/ccm71 # Adjust as appropriate informix$PATH=$CCM_HOME/bin:$PATH informix$ export CCM_HOME PATH informix$ccmsrv create [-s servername] # Repeat per db server  10. This step needs to be performed ONLY for Linux and Solaris installations that have an Informix database server and installed this Fix Pack directly on top of 7.1.0.1 or 7.1.0.2 or 7.1.0.3, without installing 7.1.0.3 iFix 001 or 7.1.0.4 or 7.1.0.5. Otherwise, skip to step 11. Unpack all databases deleted in step 2. $ 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 unpack <db_packfile> -to <dbpath> [-s servername] # Repeat per database
11. Reverse Fix Pack 7.1.0.6 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 Fix Pack installation process. The files are saved with a suffix of _p7.1.0.6. 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 Fix Pack should be replaced. For a complete list of database files that were changed see section Deliverable Synergy Components Affected.

For example <dbpath>/lib/baselib.a was replaced, to replace it with the file from before this Fix Pack:
 $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.6 <dbpath>/lib/baselib.a  Repeat this step for each database file listed in Deliverable Synergy Components Affected. 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 Fix Pack. 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 Fix Pack. Save these files and exit the editor. If the resulting files are empty then they should be deleted. 12. Unprotect the databases that were shut down in step 1, using:  ccm_root$ ccmdb unprotect <dbpath>
Repeat for every database that was patched.

13. Start the Synergy daemons using the ccm_start_daemons command.
 ccm_root$ccm_start_daemons  14. Inform users that they can restart their Synergy sessions. Installation Instructions (Microsoft 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 Fix Pack 7.1.0.6, do not install any individual iFix or Fix Pack that does not clearly state that it may be installed on top of Fix Pack 7.1.0.6, 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 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. 4. Once you have logged in as the appropriate user, run the Fix Pack executable, 7.1-RATL-RATISYNE-Windows-FP0.6.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. 5. 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 <dbpath> > ccmdb_patch_7106 <dbpath> > postdb_7106.bat <dbpath> <host> <admin_user> <admin_user_password>  6. 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://<helpserver>:<port#>/client/Update_7.1-0.6.exe.  Alternatively, the executable, Update_7.1-0.6.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 (Windows) 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 <database_path>  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 (Microsoft 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 <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.6

Before replacing the original files, you must remove the hidden attribute from files stored under the %CCM_HOME%\patches\7.1.0.6 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.6 > attrib -h * /s /d
The %CCM_HOME%\patches\7.1.0.6 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.6\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 the following files from the directory %CCM_HOME%\jetty\lib if they exist
 jetty-deploy-8.1.3.v20120416.jar jetty-http-8.1.3.v20120416.jar jetty-io-8.1.3.v20120416.jar jetty-security-8.1.3.v20120416.jar jetty-server-8.1.3.v20120416.jar jetty-servlet-8.1.3.v20120416.jar jetty-servlets-8.1.3.v20120416.jar jetty-util-8.1.3.v20120416.jar jetty-webapp-8.1.3.v20120416.jar jetty-xml-8.1.3.v20120416.jar servlet-api-3.0.jar slf4j-api-1.6.4.jar slf4j-jdk14-1.6.4.jar
Also remove the following directories from %CCM_HOME%\jetty\lib if they exist
 jndi jsp jta monitor policy spdy annotations ext
5. 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.

6. Remove 7.1.0.6 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.6.
or
 HKEY_CURRENT_MACHINE\SOFTWARE\Telelogic\CM SYNERGY\7.1\Install\Patches\7.1.0.6.

On 64 bit systems this key is located at:

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

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.6. 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 Fix Pack 7.1.0.6 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_7106.bat" to install Fix Pack 7.1.0.6 to your databases, the following three steps were performed when "ccmdb_patch_7106" was run:
• Before the Fix Pack was applied, affected database files were copied to <dbpath>\save\<filename>.p7106
• The updated files from the Fix Pack were copied to the database.
• A line was appended to <database path>\db\MDL_INFO as a record of the Fix Pack.

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.p7106 <dbpath>\lib\baselib.a
Repeat this step for each database file listed in Deliverable Synergy Components Affected (Microsoft Windows).

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

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

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, using:
 > ccmdb unprotect <dbpath>
Repeat for every database that was patched.

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

The following sections provide detailed information related to this release.

## How critical is this fix?

Impact Assessment
Impact Description
This release is a maintenance release of Synergy 7.1. It contains fixes for client reported and internally found defects.

## Known side effects

For a list of known problems refer to Known Problems.

## Change history

This Fix Pack includes the following product enhancements:

Synergy login is now case insensitive in Web mode for Windows clients.

What is Fix Central(FC)?
Link to Fix Central 14 Jun 2012 US English 1 FC

## Technical support

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.

Problems (APARS) fixed
PM20041, PM36105, PM48298, PM52746, PM53210, PM53376, PM54553, PM55580, PM55926, PM56061, PM56235, PM56455, PM56748, PM56934, PM56971, PM57240, PM57317, PM57460, PM57679, PM57819, PM57822, PM57972, PM58037, PM58079, PM58430, PM58514, PM58823, PM58859, PM58867, PM59723, PM60621, PM60623, PM60696, PM61230, PM61409, PM62736, PM62737, PM62768, PM63034, PM63045, PM63122, PM63353, PM63460, PM63930, PM64282, PM64397, PM64962

### Document information

More support for: Rational Synergy
Installation

Software version: 7.1.0.6

Operating system(s): AIX, Linux, Solaris, Windows

Reference #: 4032607

Modified date: 2013-08-27