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 changes that must be installed in Synergy databases (model changes). This Fix Pack also contains modifications to the software that must be installed in the installation directory (CCM_HOME changes).
Once you have installed Fix Pack 7.2.2.3, you should not install any individual iFix that does not clearly state that it may be installed on top of Fix Pack 7.2.2.3, 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 and Rational Synergy Integrations are running, shutdown the Change Instance.\
3. Request that all users exit their Synergy sessions before you begin the installation.
4. 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. Do not install the Fix Pack on your computer if you use a shared network installation; just install the Fix Pack once on the network installation.
5. Once you have logged in as the appropriate user, run the Fix Pack executable 7.2.2.3-RATL-RATISYNE-Windows-FP03.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.
6. To run “ccm_addsrv” command to support additional Database server configuration you must download and install "
vc_redist.x86.exe".
Open CM Command prompt as administrator on the main server and run the following command:
ccm_addsrv <mainserverhostname>
7. If you have additional Database server, Open Command Prompt as administrator on the additional database server and run below command after installing the Fix Pack 7.2.2.3-RATL-RATISYNE-Windows-FP03.exe
ccm_addsrv <mainserverhostname>
8. Start the Windows services ccm7.2.2_* from service control manager.
9. If the cache servers are installed, then the cacheserver service need to be stopped from services dialog on the cacheserver host. Once the cacheserver service is stopped, the cache server run area need to be patched by running the executable cacheserver_7.2.2.3-windows.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 on cache server. Start the cache server service once the installation is completed. Cacheserver_7.2.2.3-windows.exe will be available in the Synergy server run area under the path %CCM_HOME%\cacheserver
10. Patch databases.
Apply this Fix Pack to each of your databases. All databases must be patched prior to use with this Fix Pack.
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:\Program Files (x86) \IBM\Rational\Synergy\7.2.2
set PATH=%CCM_HOME%\bin;%PATH%
ccmdb unprotect <dbpath>
ccmdb_patch_7223 <dbpath>
postdb_7223.bat <dbpath> <host> <admin_user> <admin_user_password>
Note that passwords often contain characters that are interpreted by the shell, such as spaces, semicolons, wild cards, etc.... If this is the case, then be sure to type your admin user password in quotes.
11. Inform users that they can restart their Synergy sessions and Change instance.
This Fix Pack contains a Windows client component. Users of the Synergy Windows GUI will be prompted to download the Fix Pack when they start a session. Users of the Windows CLI will be requested to patch their clients by browsing to:
http://helpserver:port#/client/Update_7.2-2.3.exe.
Alternatively, the executable Update_7.2-2.3.exe can be distributed to Windows client users, so they can execute it directly, to update their client installations.
Reversing 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.
2. If Rational Change and Rational Synergy Integrations are running, shut down the Change Instance.
3. 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
4. Stop the 7.2.2 Synergy services. Perform this step as an admin user. Open the services dialog and stop the Synergy services.
If the cache servers are installed, then the cache server service also need to be stopped from services dialog.
5. Restore the original files replaced by Fix Pack 7.2.2.3
Before replacing the original files, remove the hidden attribute from files stored under the %CCM_HOME%\patches\7.2.2.3 directory and its sub-directories.
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.2.2.3
attrib -h * /s /d
The %CCM_HOME%\patches\7.2.2.3 directory contains two files and either three or four sub-directories. The two files are a README file and ccm_bp.in. 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 for 7.2.2.3 as there are no database components in this Fix Pack
6. The CCM_HOME directory contains a directory structure like 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.
Example:
a. Replace “ccm_exec” from %CCM_HOME%\patches\7.2.2.3\CCM_HOME\bin\util to %CCM_HOME%\bin\util
b. Replace "ccmdb" and "ccmsrv" from %CCM_HOME%\patches\7.2.2.3\CCM_HOME\bin to %CCM_HOME%\bin\
c. Remove ccm_addsrv file from %CCM_HOME%\bin
d. Change the name of file “sqlhosts.<hostname>” to "sqlhosts" from %CCM_HOME%\informix\etc
NOTE: If you are reversing from 7.2.2.3 to Synergy 7.2.2 then only the below steps need to be performed.
a. Remove ccm_addsrv file from %CCM_HOME%\bin
b. Change the name of file “sqlhosts.<hostname>” to "sqlhosts" from %CCM_HOME%\informix\etc
Edit the registry Key value "INFORMIXSQLHOSTS" from HKLM\SOFTWARE\Informix\OnLine\<INFORMIXSERVER>\Environment.
Modify key value to %CCM_HOME%\informix\etc\sqlhosts
7. Remove entries in patches.txt and patches.dat in both Synergy server and also from cache servers if they were patched.
In the %CCM_HOME%\etc directory are files “patches.txt” and “patches.dat”.
a. Using a text file editor (such as Notepad.exe)
b. Edit these files and remove the lines referencing this Fix Pack.
c. Save this file and exit the editor.
d. If the resulting files are empty, then delete them.
8. Remove 7.2.2.3 Key from the Registry.
a. Start the registry editor (Click Start > Run type regedit)
b. Browse to the appropriate key listed below.
c. You will see a key labelled 7.2.2.3. Click it. (HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\CM SYNERGY\7.2.2\Install\Patches\7.2.2.3)
d. Delete the key (press Delete on keyboard).
e. Exit the registry editor.
NOTE: Repeat the above steps for Additional DB server also while reversing Fix Pack
9. Reverse Fix Pack 7.2.2.3 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_7223.bat to install Fix Pack to your databases, the following steps are performed when "ccmdb_patch_7223" is run:
Before the Fix Pack is applied, affected database files are copied to <dbpath>\save\<filename>.p7223
The updated files from the Fix Pack are copied to the database.
A line is 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.
a. Log in as CM administrator on the database server machine and bring up a command window.
b. Remove the database files that were changed:
c. del <dbpath>\lib\apilib.a
d. Move the saved copy of these files back into their original locations:
move <dbpath>\save\lib\apilib.a.p7223 <dbpath>\lib\apilib.a
e. Repeat this step for each database file listed in Database files affected by the Fix pack.
In the <database path>\db directory, there is a file named MDL_INFO.
Using a text file editor (such as 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 (such as 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
10. Restart the services that were stopped in step 2. Open the services dialog and start the Synergy services.
11. Also, If the cache servers are installed, then the cacheserver service also need to be restarted from services dialog.
12. Unprotect the databases that were shut down in step 3.
ccmdb unprotect <dbpath>
Repeat for every database.
13. Inform users that they can restart their Synergy sessions and Change instance.
* Jetty is upgraded to ver. 9.4.35