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.

Prerequisites

Installation Instructions

Review the Installing section of the knowledge center for complete details.

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.

Installation Instructions (UNIX and Linux)

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

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

Once you have installed Fix Pack 7.2.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.2.0.6, unless informed otherwise by Synergy Support.

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 Rational Synergy ccm_patch installer script (ccm_patch) for UNIX. 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).

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

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

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

This step needs to be performed only for Linux and Solaris installations that use an Informix database, and have not already installed Fix Pack 7.2.0.5 (you are upgrading directly from 7.2 to 7.2.0.6).

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

ccm_root$ ccm_start_daemons

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 Fix Pack 7.2.0.5 (you are upgrading directly from 7.2 to 7.2.0.6).

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 the Windows CLI will be requested to patch their clients by browsing to

http://<helpserver>:<port#>/client/Update_7.2-0.6.exe

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

Reversing the Fix Pack (UNIX & Linux)

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.

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.

Steps 2 - 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.2, without first installing 7.2.0.1 or 7.2.0.2 or 7.2.0.3 or 7.2.0.4 or 7.2.0.5. Otherwise, skip to step 5.

Delete all databases

ccm_root$ ccm delete <dbpath> # Repeat per database

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.2, without first installing 7.2.0.1 or 7.2.0.2 or 7.2.0.3 or 7.2.0.4 or 7.2.0.5. Otherwise, skip to step 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.2, without first installing 7.2.0.1 or 7.2.0.2 or 7.2.0.3 or 7.2.0.4 or 7.2.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. If the server is offline, then bring the server online to get the information and then make it offline again.

Also remove the following directories from $CCM_HOME/jetty/lib if they exist

jndi jsp jta monitor policy spdy annotations ext

Restore the installation files from before Fix Pack 7.2.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.2.0.6. 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 Fix Pack. For a complete list of $CCM_HOME files that were changed, review the Deliverable Synergy Components Affected section. For example, $CCM_HOME/lib/ccmjava.jar was replaced. To replace it with the file from before this Fix Pack:

Steps 10 - 11 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.2, without first installing 7.2.0.1 or 7.2.0.2 or 7.2.0.3 or 7.2.0.4 or 7.2.0.5. Otherwise, skip to step 12.

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.2, without first installing 7.2.0.1 or 7.2.0.2 or 7.2.0.3 or 7.2.0.4 or 7.2.0.5 . Otherwise, skip to step 12. If the patch 7.2.0.6 is directly installed on top of 7.2 then skip steps 12 and 13.

Unpack all databases deleted in step 2 and add them to active database list once the daemon services are started

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.2.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, review the Deliverable Synergy Components Affected section.

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

Installation Instructions (Microsoft Windows)

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

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.2.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.2.0.6, unless informed otherwise by Synergy Support.

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

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

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.

Once you have logged in as the appropriate user, run the Fix Pack executable, 7.2-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.

Patch standard databases.

If you do not have a customized model, 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, 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:

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.

Inform users that they can restart their Synergy sessions.

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

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

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.

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

Stop the 7.2 Synergy services. Perform this step as 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.

Restore the original files replaced by Fix Pack 7.2.0.6

Before replacing the original files, remove the hidden attribute from files stored under the %CCM_HOME%\patches\7.2.0.5 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.2.0.5 > attrib -h * /s /d

The %CCM_HOME%\patches\7.2.0.6 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 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 %CCM_HOME%\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

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.

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.

Known side effects

Change history

What's new

This fix pack supports MSSCCI integration between Synergy 7.2.0.6 and Powerbuilder 12.5. The details can be found in the documents readme.htm and powerbuilder_help.pdf under the location %ccm_home%\integrations\powerbuilder.

Technical support

Tab navigation

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.