Preserving the CM Server configuration

You need to preserve the Change Management (CM) Server MBean configuration before customizing the MBean attributes, or upgrading from, or reinstalling Rational® ClearQuest® 7.1.x.y, or 8.0.x.y. If you do not preserve the configuration, any customization that you have made is lost.

About this task

If your Rational ClearQuest and ClearQuest 7.1.0.x, or 8.0.x.y, installation includes the WAN support packages, then the CM Server components are also installed. To determine if the WAN support packages are installed, check if the CM subdirectory is installed in the DevOps common directory:

On Windows: %RATIONAL_INSTALL%\%RATIONAL_COMMON%\
On the UNIX system and Linux: $RATIONAL_INSTALL/$RATIONAL_COMMON/

where the variables have the following meanings:

RATIONAL_INSTALL: Directory where the DevOps software is installed
RATIONAL_COMMON: DevOps common directory

Note: Before upgrading from, or reinstalling, Rational ClearQuest 7.1.x.y, you must preserve the CM Server MBean configuration because the installer does not. If you do not perform this task before upgrading or reinstalling, any customization is lost.

It is also a good practice to export the MBean configuration prior to modifying any of the CM Server MBean attributes by using the wsadmin scripts included with the installed CM Server components. This allows you to restore the MBean values to a known working configuration if the new settings produce undesirable results.

You must run the wsadmin scripts while the CM Server components, including WebSphere® Application Server, are running. Note that you can automate the procedure of capturing the CM Server MBean configuration on a periodic basis by creating an AT job on Windows or a cron job on the UNIX system or Linux.

The following is the default location of the CM Server wsadmin utility scripts:

On Windows: C:\Program Files\IBM\CM\scripts
On the UNIX system and Linux: /opt/CM/scripts

Note: If only DevOps Code ClearCase® or only Rational ClearQuest is installed, then you must follow the instructions in the next section "Procedure for Manually Preserving the MBean Configuration Settings" instead of using the instructions in this section.

Procedure

Procedure for exporting and importing MBean configuration settings

In a command prompt window, set the default directory to the location of the CM Server wsadmin utility scripts. For example:
- On Windows:# cd "C:\Program Files\IBM\CM\scripts"
- On the UNIX system and Linux: # cd /opt/CM/scripts
Set the path to the wsadmin utility by using the syntax appropriate for your shell. For example:
- On Windows: # set WAS_BIN="C:\Program Files\IBM\eWAS\bin"
- On the UNIX system and Linux: # WAS_BIN=/opt/eWAS/bin
Start the wsadmin utility by specifying the CM Server profile name. By default, the CM Server profile name is cmprofile. For example:
- On Windows: # %WAS_BIN%\wsadmin -profileName cmprofile
- On the UNIX system and Linux: # $WAS_BIN/wsadmin.sh -profileName cmprofile
Load the JACL scripts, which include the exportToFile and importFile commands, into your wsadmin command shell: wsadmin> source teamAdminUtils.jacl
Export the MBean configuration to a file that is outside the CM Server installation directory structure.
Note: On Windows, when you run a JACL script from the wsadmin command shell, you can use forward slashes '/' in the path specification that you pass to the JACL script. Alternatively, if you choose to use backslashes '\', you must escape each backslash character with an additional backslash. For example:
- On Windows: wsadmin> exportToFile C:/temp/CmServer_backups/MBean.bck
- On the UNIX system and Linux: wsadmin> exportToFile /tmp/CmServer_backups/MBean.bck
You can use the importFile command to restore a saved MBean configuration. Use this command after you upgrade or reinstall the CM Server components, or after you make MBean configuration changes, and you want to roll back to a previous configuration.

Procedure for Manually Preserving the MBean Configuration Settings

If only DevOps Code ClearCase or only Rational ClearQuest are installed, you must follow the instructions in this section. Otherwise, if DevOps Code ClearCase and Rational ClearQuest are both installed, use the instructions in the previous section "Procedure for exporting and importing MBean configuration settings."

In a command prompt window, set the default directory to the following location, replacing the following variables, as appropriate:
- Replace cmprofile if the default profile name is not used
- Replace <computer-name>CMProfileNode01Cell, dfltCell,<computer-name>CMProfileNode01, or dfltNode with the cell name and node name
For example:
- On Windows:# cd "C:\Program Files\IBM\CM\profiles\cmprofile\config\cells\ <computer-name>CMProfileNode01Cell\nodes\<computer-name>CMProfileNode01\servers\server1\stp"
- On the UNIX system and Linux: # cd /opt/rational/common/CM/profiles/cmprofile/config/ cells/dfltCell/nodes/dfltNode/servers/server1/stp
Copy all .dat files from the default directory to a temporary directory outside the CM Server installation directory structure. For example:
- On Windows: # copy *.dat C:\temp\CmServer_mbean_config_files
- On the UNIX system and Linux: # cp *.dat /tmp/CmServer_mbean_config_files
After upgrading DevOps Code ClearCase and Rational ClearQuest, ensure that the CM Server components are not running. Follow the instructions from the Starting, stopping, and restarting CM Server topic, to stop the CM Server components.
Open a command prompt window. As the root user, set the default directory to the location described in step 6. Then copy the saved .dat files from the temporary directory used in step 7, into the default directory. For example:
- On Windows: # copy C:\temp\CmServer_mbean_config_files\*.dat
- On the UNIX system and Linux: # cp /tmp/CmServer_mbean_config_files/*.dat
When the CM Server components are started, the data from the restored .dat files are used to initialize the MBean attributes.