Ensure that you have installed Rational Directory Server 5.1.1 (Apache) or 5.2 (Tivoli®). For information about installing Rational Directory Server, see the IBM Rational Directory Server information center.
If you have a previous Rational Directory Server, you must migrate your users and data to the new server.
If you plan to use the project security feature, see Managing project security and Planning for more details.
If you use Rational Change Distributed, see information about compatibility with IBM Rational Synergy Distributed in the "Administering > Administering Rational Synergy Distributed" section of the IBM Rational Synergy information center.
You can upgrade customizations performed using the Lifecycle Editor. Copy your XML file to the new Rational Change 5.3 CHANGE_APP_HOME/WEB-INF/cr_process directory, load the XML file, and follow the instructions in the window that opens. In most cases, all that is required is saving the XML file, creating the package, and then installing the package.
You can also upgrade a customization that was made manually. However, depending on the extent of the customization, additional work might be required to make it compatible with Rational Change 5.3.
Save your manual customizations in a package template. If you have done so, copy your package template into the Rational Change 5.3 CHANGE_APP_HOME/WEB-INF/package_templates directory. Then, use the package template to re-create your package.
You must apply customizations that were made in the ptcli.cfg file.
In version 5.2 and later, this file is located in:
CHANGE_APP_HOME/WEB-INF/wsconfig
In versions before 5.2, the file is located in $CCM_HOME/etc.
If you use pre- and post-transition TRELATIONs, they are no longer supported. Their functions can be duplicated with bean scripting framework (BSF) trigger scripts, found in the CHANGE_APP_HOME/WEB-INF/wsconfig/triggers directory. Although the built-in TRELATIONs are automatically mapped to the replacement BSF scripts when the CR process is upgraded, other TRELATIONs might require manual replacement.
A central server cluster consists of a central server and one or more remote servers. Always upgrade the central server first, as its release level must be greater than or equal to that of its remote servers. The central server must be the most up-to-date server in the cluster.
The remainder of this section contains information about how to handle issues with a heterogeneous encoding environment in Central Server Mode.
Rational Change 5.2 and earlier releases supported either the CP1252 or UTF-8 character encoding. The UTF-8 encoding was only applicable with the Asian-line of Rational Synergy. However, the products did not support heterogeneous encoding between servers in a central server cluster. The encodings were either all UTF-8 or all CP1252.
As of Rational Change 5.3, UTF-8 is the only supported encoding. It might not be possible to upgrade all servers in a CP1252 central server cluster to UTF-8 at once. Therefore, a heterogeneous encoding environment might result during the upgrade.
If you are upgrading from version 4.7 or older, attribute controls (for example, base.CCM_LISTBOX) were updated in Rational Change 5.0. Most of the JavaScript that previously existed in the controls has been extracted into the file CHANGE_APP_HOME/trapeze/js53/ctrlUtils.js, which is included on base templates. While an effort was made to preserve compatibility with earlier versions, certain types of customizations, such as interdependent controls, must be manually upgraded.