Tip: Upgrade script workaround for distributed deployments where systems have different architecture (32 bit vs 64 bit)

Author: Heather Sterling
Last Updated: June 13, 2011
Build basis: Rational Team Concert 3.0.1, Rational Requirements Composer 3.0.1, Rational Quality Manager 3.0.1

Summary

If you are performing an upgrade with an upgrade script and the JTS and application server have differing architecture, you may need to use several workarounds to complete the upgrade successfully. Alternatively, you can follow the steps contained in this article for upgrading manually without the ability to mount drives.

More Information

Several commands used by the upgrade script invoke other commands that do not function properly when invoked on a system with a different architecture. For example, if your setup includes CCM on a 32-bit system with a shared JTS on a 64-bit system, you will hit errors during the upgrade execution. The errors occur when the upgrade script on the application system attempts to execute a repotools command remotely on a JTS system of differing architecture.

Diagnosing the problem:

On Microsoft® Windows, the following error message will occur during step 0 (updateConfigurationFiles) or step 3 (importApplicationData) of the upgrade.

CRJAZ2107E The Jazz Team Server compatibility check failed with a machine type mismatch error. The machine type of the application system and the target Jazz Team Server system must be the same, either both 32-bit or both 64-bit. If this is not the case, follow the instructions in the InfoCenter for a distributed deployment where drive-mapping is not possible.

There is currently no CLM error message for non-Windows platforms and we do not have the full list of OS error messages for every supported platform. The error should indicate a machine type mismatch with the java command.

Working around the problem:

JTS 3.0:

• No workaround is required since no remote JTS command is issued.

RM 2.X:

• No workaround is required since the RM upgrade is run from the JTS system.

CCM 3.0:

• Step 0: Validate that the JTS has already been upgraded to 3.0.1. Run the upgrade script with the -ignoreJTSVersionCheck flag.

CCM 2.x:

• Validate that the JTS has already been upgraded to 3.0.1.
• Start script execution on the CCM system with the -ignoreJTSVersionCheck flag.
• Step 0: Verify that the -ignoreJTSVersionCheck flag is set.
• Step 3: Stop the script execution here. Run Step 3 manually from the JTS machine. This will require you to move files between the JTS and CCM systems or mount a drive to the CCM system from the JTS system.
• Resume script execution at step 4 on the CCM system.

QM 2.x:

• Validate that the JTS has already been upgraded to 3.0.1.
• Start script execution on the QM system with the -ignoreJTSVersionCheck flag.
• Step 0: Verify that the -ignoreJTSVersionCheck flag is set.
• Step 3: Stop the script execution here. Run Step 3 manually from the JTS machine. This will require you to move files between the JTS and QM systems or mount a drive to the QM system from the JTS system.
• Resume script execution at step 4 on the QM system.

Related Information

The following links point to related information:

• document what to do if JTS and CLM app to be upgraded are on 32 bit & 64 bit respectively (163859)
• no warnings for 2.x to 3.0.1 Upgrade with 32bit application server and 64bit JTS server (168383)