Skip to content

Synergy 1.3.7 Download

Posted on by admin

Download latest version of Synergy. Application controls keyboard and mouse for ease-of-use, automation and remote access.

Synergy is a cross-platform, open-source replacement for a KVM switch. Instead of looping multiple computers through a piece of hardware, it lets you control them from a single keyboard and mouse. As a software solution, you might want to just go with the KVM switch. Synergy can be extremely difficult to configure, especially determining precise computer names and server locations. Even though the program lets you rename computers with simpler aliases, it can still be challenging to configure Synergy properly. The interface is uninspired, but at least it's not confusing.

  • Download synergy 1.3.7 for windows 7 - Web Archive Downloader 1.3.7: Internet archive downloader., and much more programs.
  • Synergy, free and safe download. Synergy latest version: Control many computers with the same keyboard and mouse. If you work between several different machines.

Once you get Synergy running, you can switch from one computer to the next simply by push your mouse off-screen. You can configure that switching location to be on any or all of the four sides of your main monitor. Users can also configure screensavers to start simultaneously, and can link log-in information so that one hard drive doesn't hibernate while you're working on another one. The clipboards can also be linked, making it dead easy to transfer small chunks of information, such as URLs, from one system to the next. This is a difficult program to set up properly, but it works well once going and might even be considered a must-have, or at least a must-try, for anybody who uses more than one computer at a time. From Synergy lets you easily share a single mouse and keyboard between multiple computers with different operating systems each with its own display without special hardware.

Download

It is intended for users with multiple computers on their desk since each system uses its own monitor(s). Redirecting the mouse and keyboard is as simple as moving the mouse off the edge of your screen. Synergy also merges the clipboards of all the systems into one, allowing cut-and-paste between systems. Furthermore, it synchronizes screen savers so they all start and stop together and, if screen locking is enabled, only one screen requires a password to unlock them all.

Table of Contents Sections Description. The Change history section provides an overview on what is new in this release with a description of any new functions or enhancements when applicable. The How critical is this fix section provides information related to the impact of this release to allow you to assess how your environment may be affected. The Prerequisites section provides important information to review prior to the installation of this release.

The Download package section provides the direct link to obtain the download package for installation in your environment. The Installation instructions section provides the installation instructions necessary to apply this release into your environment. The Known side effects section contains a link to the known problems (open defects) identified at the time of this release. Supporting Documentation Document Description. 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.

IBM Knowledge Center provides an entry point to product documentation. You can view, browse, and search online information related to the product.

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. Find technical developer content and resources. Review the installation guide: Where to Apply this Fix Pack Apply this Fix Pack to all Synergy installations (CCMHOME), clients and cache servers. First install to the machine where the Synergy router daemon is running, then install to other server machines, and finally deploy to client machines and cache servers. Table of Contents Deliverable Synergy Components Affected Those marked with an asterisk (.) have changed since 7.2.1.2 iFix 001. Installation Instructions (UNIX and Linux) Before you begin, make sure that you have performed a successful backup of your Synergy installation areas.

Note: If this fix pack is not upgraded from 7.2.1.2 iFix 001, then it requires that RDS tdsadmin credentials are configured appropriately for authentication through RDS. Failing to do so, would result in authentication not working. Please refer to step 6 for more details. Refer to security bulletin for details on security vulnerability in RDS. This Fix Pack contains modifications to the software that must be installed in the installation directory ( CCMHOME changes).

This Fix Pack also contains changes that must be installed in Synergy databases (model changes). This Fix Pack also contains changes for cache server and if there are any cache servers installed then they must be updated(Cache server changes). Once you have installed Fix Pack 7.2.1.3, 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.1.3, unless informed otherwise by Synergy Support. To install this Fix Pack on UNIX, use the ccmpatch script. If you do not have the ccmpatch script, please download it from the If you have previously downloaded a copy of ccmpatch, 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 ccmpatch is 47. If you have downloaded a newer version, then copy the ccmpatch script to $CCMHOME/bin in each server installation; make sure it is owned by ccmroot 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 ccmroot and set CCMHOME to point to your Synergy installation. Shut down all Synergy 7.2.1 databases.

Verify that all users have exited by using the ccm monitor command. $ su - ccmroot ccmroot$ CCMHOME=/usr/local/ccm721 # Adjust as appropriate ccmroot$ PATH=$CCMHOME/bin:$PATH ccmroot$ export CCMHOME PATH ccmroot$ ccmdb shutdown # Repeat per database ccmroot$ ccm monitor Stop the Synergy daemons using the ccmstopdaemons command. Ccmroot$ ccmstopdaemons If there are cache servers installed and running, they also need to be stopped. (Run the commands on the cache server system, if the cache servers are running on Windows platform, refer the Windows installation section) $ su - ccmroot ccmroot$ CCMHOME=/usr/local/ccm721 # Adjust as appropriate ccmroot$ PATH=$CCMHOME/bin:$PATH ccmroot$ export CCMHOME PATH ccmroot$ cd $CCMHOME/bin ccmroot$./ccmcache -stop. Update the Synergy installation directory.

Use the ccmpatch command. The argument to ccmpatch is the full path to the Fix Pack file that you are installing.

Note that ccmpatch must be run as root, since it needs to set ownership and permissions on the patched files. Ccmroot$ su # CCMHOME=/usr/local/ccm721 # Adjust as appropriate # PATH=$CCMHOME/bin:$PATH # export CCMHOME PATH If your database runs on Oracle then set ORACLEHOME. # ORACLEHOME=/usr/local/oracle # Adjust as appropriate # export ORACLEHOME Use the tar file that is appropriate for your UNIX platform.

For AIX: # ccmpatch /7.2-RATL-RATISYNE-AIX- FP1.3.tar.gz For HP-UX: # ccmpatch /7.2-RATL-RATISYNE-HPUX- FP1.3.tar.gz For Linux: # ccmpatch /7.2-RATL-RATISYNE-Linux- FP1.3.tar.gz For Solaris: # ccmpatch /7.2-RATL-RATISYNE-Solaris- FP1.3.tar.gz # exit Repeat this command for each installation directory. Once the installation directory has been updated, restart the Synergy daemons as the ccmroot user.

Ccmroot$ ccmstartdaemons If there are cache servers installed, they also need to be updated. (Run the commands on the cache server system, if the cache servers are running on Windows platform, refer the Windows installation section) ccmroot$ su # CCMHOME=/usr/local/ccm721 # Adjust as appropriate # PATH=$CCMHOME/bin:$PATH # export CCMHOME PATH # cd $CCMHOME/bin Use the tar file that is appropriate for your UNIX platform. The tar files will be available in the Synergy run area under the path CCMHOME/cacheserver For AIX: # cacheserverpatch / cacheserver 7.2-1.3 -aix.tar.gz For HP-UX: # cacheserverpatch / cacheserver 7.2-1.3 -hpux.tar.gz For Linux: # cacheserverpatch / cacheserver 7.2-1.3 -linux.tar.gz For Solaris: # cacheserverpatch / cacheserver 7.2-1.3 -solaris.tar.gz # exit Repeat this command for each installation directory. Once the installation directory has been updated, restart the Synergy cache server as the ccmroot user. Ccmroot$ ccmcache -start. Configure RDS tdsadmin user credentials Once the installation directory has been updated, configure RDS tdsadmin user credentials as the ccmroot user.

Ccmroot$ setuprds Provide tdsadmin password when prompted. Use the ccmpatch command to apply this Fix Pack to one or more databases. If you have a customized model using a custom model database, contact Synergy Support for assistance. Databases that were shut down in step 4 must be unprotected prior to patching. $ su - ccmroot ccmroot$ CCMHOME=/usr/local/ccm721 # Adjust as appropriate ccmroot$ PATH=$CCMHOME/bin:$PATH ccmroot$ export CCMHOME PATH ccmroot$ ccmdb unprotect ccmroot$ ccmpatch -dbonly $CCMHOME/patches/ 7.2.1.3.

Synergy 7.2.1.3 is a cumulative fix pack, so it includes all the fixes done in the previous fix packs and iFixes on 7.2.1 stream. If the upgrade path followed for 7.2.1.3 fix pack is same for Synergy server run area, Synergy databases and Synergy client run areas, then ignore this step. If the upgrade path is different for one of Synergy server run area, Synergy databases and Synergy client run areas and Synergy 7.2.1.3 fix pack installer is downloaded after 6-November-2014, then ignore this step. If the upgrade path is different for one of Synergy server run area, Synergy databases and Synergy client run areas and Synergy 7.2.1.3 fix pack installer is downloaded before 6-November-2014, then follow the the solution provided in the tech note to resolve the incompatibility error. 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 the Windows CLI will be requested to patch their clients by browsing to: Alternatively, the executable, Update7.2-1.3.exe, can be distributed to Windows CLI users, so they can execute it directly, to update their client installations. Post Installation Instructions (UNIX & Linux). If you have a DCM cluster that has a mix of 7.2 databases with 7.0 or 7.1 databases, then create two attributes on the model object as follows. Attribute name Attribute type Value maxobjectnamelength integer 155 maxobjectversionlength integer 32 This will ensure that objects created in the 7.2 database conform to the length restrictions in the 7.0 or 7.1 databases. The ccm.properties setting ccm.changerequesttool.timeout, which controls the time-out for a Change operation initiated from Synergy, was replaced by a pair of settings: ccm.changerequesttool.timeout - used for operations after Change startup ccm.changerequesttool.startup.timeout - used for Change startup If Synergy users invoking Change operations see errors such as the following in the log files, the time-out values should be adjusted. CRCCM4004: An I/O problem occurred while communicating with IBM Rational Change at The reported error was: java.net.SocketTimeoutException:Read timed out. 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. 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 ccmroot, shut down all Synergy databases that use this installation. Verify that all users have exited by using ccm monitor.

$ su - ccmroot ccmroot$ CCMHOME=/usr/local/ccm721 # Adjust as appropriate ccmroot$ PATH=$CCMHOME/bin:$PATH ccmroot$ export CCMHOME PATH ccmroot$ ccmdb shutdown # Repeat per database ccmroot$ ccm monitor Stop the Synergy daemons using the ccmstopdaemons command. Ccmroot$ ccmstopdaemons If the cache servers are running, they also need to be stopped. (Run the commands on the cache server system, if the cache servers are running on Windows platform, refer the Windows installation section) $ su - ccmroot ccmroot$ CCMHOME=/usr/local/ccm721 # Adjust as appropriate ccmroot$ PATH=$CCMHOME/bin:$PATH ccmroot$ export CCMHOME PATH ccmroot$ cd $CCMHOME/bin ccmroot$./ccmcache -stop. Restore the installation files from before Fix Pack 7.2.1.3 $CCMHOME 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.1.3. 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 $CCMHOME files that were changed, review the section.

For example, $CCMHOME/lib/ccmjava.jar was replaced. To replace it with the file from before this Fix Pack: $ su - ccmroot ccmroot$ CCMHOME=/usr/local/ccm721 # Adjust as appropriate ccmroot$ PATH=$CCMHOME/bin:$PATH ccmroot$ export CCMHOME PATH ccmroot$ cp $CCMHOME/save/lib/ccmjava.jar p7.2.1.3 $CCMHOME/lib/ccmjava.jar Repeat this step for each $CCMHOME file listed in section. Repeat this step for the files in cache server run area also if the cache server was patched.

Remove entries in patches.txt and patches.dat in both Synergy server and also from cache servers if they were patched. In the $CCMHOME/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 delete them. Login as user root.

You need to run $CCMHOME/bin/ccminstall in order to reset the ownership and permissions of the original files you copied back: $ su - # CCMHOME=/usr/local/ccm721 # Adjust as appropriate # PATH=$CCMHOME/bin:$PATH # export CCMHOME PATH If your database runs on Oracle then set ORACLEHOME # ORACLEHOME=/usr/local/oracle # Adjust as appropriate # export ORACLEHOME # ccminstall -c # exit If the cache server was patched then Login as user root on cache server. You need to run $CCMHOME/bin/cacheserverinstall in order to reset the ownership and permissions of the original files you copied back: $ su - # CCMHOME=/usr/local/ccm721 # Adjust as appropriate # PATH=$CCMHOME/bin:$PATH # export CCMHOME PATH # cacheserverinstall -c # exit.

Reverse Fix Pack 7.2.1.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. 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.1.3. 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 section. For example /lib/baselib.a was replaced, to replace it with the file from before this Fix Pack: $ su - ccmroot ccmroot$ CCMHOME=/usr/local/ccm721 # Adjust as appropriate ccmroot$ PATH=$CCMHOME/bin:$PATH ccmroot$ export CCMHOME PATH ccmroot$ cp /save/lib/baselib.a p7.2.1.3 /lib/baselib.a Repeat this step for each database file listed in the section. In the /db directory of each database is a file named MDLINFO. Using an editor, for instance vi, edit these files. Remove the lines referencing this Fix Pack. In the /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. Unprotect the databases that were shut down in step 1, using: ccmroot$ ccmdb unprotect Repeat for every database that was patched.

Start the Synergy daemons using the ccmstartdaemons command. Ccmroot$ ccmstartdaemons If the cache server was patched, then start the cache server using the ccmcache command. Ccmroot$ ccmcache -start. 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 Installation areas. Note: If this fix pack is not upgraded from 7.2.1.2 iFix 001, then it requires that RDS tdsadmin credentials are configured appropriately for authentication through RDS. Failing to do so, would result in authentication not working.

Please refer to step 5 for more details. Refer to security bulletin for details on security vulnerability in RDS. This Fix Pack contains modifications to the software that must be installed in the installation directory ( CCMHOME changes). This Fix Pack also contains changes that must be installed in Synergy databases (model changes).

This Fix Pack also contains changes for cache server and if there are any cache servers installed then they must be updated(Cache server changes). Once you have installed Fix Pack 7.2.1.3, 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.1.3, 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.

Synergy 1.3.8 Download

ccmdb shutdown # 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-FP1.3.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. If the cache servers are installed, then the cacheserver service need to be stopped from services dialog.

Once the cacheserver service is stopped, the cache server run area need to be patched by running the executable cacheserver7.2.1.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. Cacheserver7.2.1.3-windows.exe will be available in the Synergy server run area under the path CCMHOME/cacheserver. Configure RDS tdsadmin user credentials Once the installation has been completed, configure RDS tdsadmin user credentials set CCMHOME=c: ccm72 # Adjust as appropriate set PATH=%CCMHOME% bin;%PATH% setuprds.bat Provide tdsadmin password when prompted. 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: set CCMHOME=c: ccm721 # Adjust as appropriate set PATH=%CCMHOME% bin;%PATH% ccmdb unprotect ccmdbpatch 7213 postdb 7213.bat Note that passwords often contain characters that are interpreted by the shell, such as spaces, semicolons, wild cards, etc.

Synergy Download Windows 10

If this is the case, then be sure to type your admin user password in quotes. Synergy 7.2.1.3 is a cumulative fix pack, so it includes all the fixes done in the previous fix packs and iFixes on 7.2.1 stream. If the upgrade path followed for 7.2.1.3 fix pack is same for Synergy server run area, Synergy databases and Synergy client run areas, then ignore this step. If the upgrade path is different for one of Synergy server run area, Synergy databases and Synergy client run areas and Synergy 7.2.1.3 fix pack installer is downloaded after 6-November-2014, then ignore this step. If the upgrade path is different for one of Synergy server run area, Synergy databases and Synergy client run areas and Synergy 7.2.1.3 fix pack installer is downloaded before 6-November-2014, then follow the the solution provided in the tech note to resolve the incompatibility error. 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:. Alternatively, the executable, Update7.2-1.3.exe, can be distributed to Windows CLI users, so they can execute it directly, to update their client installations. Post Installation Instructions (Microsoft Windows). If you have a DCM cluster that has a mix of 7.2 databases with 7.0 or 7.1 databases, then create two attributes on the model object as follows.

Attribute name Attribute type Value maxobjectnamelength integer 155 maxobjectversionlength integer 32 This will ensure that objects created in the 7.2 database conform to the length restrictions in the 7.0 or 7.1 databases. The ccm.properties setting ccm.changerequesttool.timeout, which controls the time-out for a Change operation initiated from Synergy, was replaced by a pair of settings: ccm.changerequesttool.timeout - used for operations after Change startup ccm.changerequesttool.startup.timeout - used for Change startup If Synergy users invoking Change operations see the following errors in the log files, the time-out values should be adjusted.

CRCCM4004: An I/O problem occurred while communicating with IBM Rational Change at The reported error was: java.net.SocketTimeoutException:Read timed out. 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 # repeat per database ccm monitor. Stop the 7.2.1 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.

If the cache servers are installed, then the cacheserver service also need to be stopped from services dialog. Restore the original files replaced by Fix Pack 7.2.1.3 Before replacing the original files, remove the hidden attribute from files stored under the%CCMHOME% patches 7.2.1.3directory 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%CCMHOME% patches 7.2.1.3 attrib -h. /s /d The%CCMHOME% patches 7.2.1.3 directory contains two files and either three or four sub-directories. The two files are a README file and ccmbp.in. You do not need to be concerned with the ccmbp.ini file. The three sub-directories that every installation will have are CCMHOME, 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 CCMHOME 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 CCMHOME 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%CCMHOME% 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%CCMHOME% patches 7.2.1.3 CCMHOME lib to the directory%CCMHOME% lib Restore all CCMHOME files replaced by this Fix Pack.

For a complete list of CCMHOME files replaced, please see the above section titled,. Repeat this step for the files in cache server run area also if the cache server was patched.

Remove entries in patches.txt and patches.dat in both Synergy server and also from cache servers if they were patched. In the%CCMHOME% etc directory are files patches.txt and patches.dat. Using a text file editor (such as 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 delete them. Remove 7.2.1.3 Key from the Registry. Start the registry editor (Click Start Run type regedit).

1.3.7

Browse to the appropriate key listed below. You will see a key labeled 7.2.1.3.

Delete the key (press Delete on keyboard). Exit the registry editor. Regression: An error in the (MDV) that produces incorrect or unexpected behavior causing a supported feature to stop functioning as designed. This includes:.

Lfs s2 alpha x keygen crack. Download Live For Speed S2 Alpha With Keygen Full Version PC Game.

Coding errors that cause a regression. Documentation or packaging problems that cause a regression.

Errors reported in a new function delivered in a MDV that cause a regression Incomplete: An error in the MDV has not regressed, but does not work as designed. This includes:. Fixed APARs which did not solve the original problem but did not break anything new. APARs reporting documentation errors, such as readme errors, that cause problems applying an MDV but do not lead to a regression Notes:. Regression and incomplete APARs are considered fix-in-error or MDV-in-error.

Definitions above apply only to valid APARs that result in product fixes (APARs returned as working-as-designed are not assessed for being fix-in-error). Issues in major releases due to new functionality do not apply in this definition. APAR Internal ID Description/Workaround Status R#45221 Upgrading databases on 721 run area which has been upgraded from an existing 71 run area(only on Windows) fails from second attempt The first command(ccmdb upgrade) to upgrade a 71 database in 721 succeeds without any issues. The subsequent upgrade commands to upgrade a 71 database in 721 fails.

Workarounds:. For each ccmdb upgrade, restart the services. Pack the database using 'ccmdb pack' command and unpack the pack file in 721 and do an upgrade. No plan to fix R#45278 Unhandled Runtime Exception gets reported in Synergy GUI when synergy server is restarted and Synergy-RTC integration is enabled Workaround Restarting Synergy GUI solves the problem No plan to fix Open defects Review the following on the IBM Support Portal. Review technote for information on how to configure your MyNotifications subscription account and subscribe to the APARs you are interested in following.

IBM Rational Software Support Communities. Visit the to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information. Visit 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. Visit the 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. Follow IBM Rational Client Support on.