How to upgrade CA Software Change Manager (SCM) 7.0 to CA SCM 12.0 on Windows

Document ID : KB000054418
Last Modified Date : 14/02/2018
Show Technical Document Details

Description

This document features a strategy to upgrade Windows SCM 7.0 users to SCM 12.0, so that they don't have to go through intermediate step of a full upgrade to SCM 7.1 and then to SCM 12.0.

This migration procedure only applies for SCM installations with Oracle Database.

Note: CA Software Change Manager (SCM) 7.0 references made in this document was previously known as AllFusion Harvest Change Manager 7.0

Solution

CA SCM 12.0's upgrade routine can only upgrade SCM 7.1 software/database to SCM 12.0 standards. So, SCM 7.0 users are required to upgrade to SCM 7.1 for migration to SCM 12.0

This document features some scenarios to upgrade Windows SCM 7.0 users to SCM 12.0, so that they don't have to go through intermediate step of a full upgrade to SCM 7.1 and then to SCM 12.0. This migration procedure only applies for SCM installations with Oracle Database. Briefly, the procedure refers to identifying the existing components, backup up of required files, uninstall of existing components, upgrade database and install of SCM 12.0.

This document is NOT a replacement/substitute of the existing SCM 12.0 Implementation Guide.

Minimum Requirements:

If you have not already done so, read the Release Notes to ensure that your DBMS version is supported for SCM 7.0. If your DBMS version does not meet the requirements listed in the Release Notes, upgrade it to a supported release before upgrading the server.

Note: You can find the most current version of the Release Notes at http://ca.com/support.

Identify Existing Components:

Next step is to identify all existing SCM components on the SCM host and where they're installed:

  1. Invoke Windows Start -> Control Panel -> Add/Remove Programs


    (Note: If it is a Microsoft Windows XP/2003 operating system, make sure Show Updates option on this dialog box is checked ON to show updates/efixes/hotfixes)

  2. Verify the SCM 7.0 components installed

    1. Program AllFusion Harvest Change Manager Client indicates SCM 7.0 Client

    2. Program AllFusion Harvest Change Manager Server indicates SCM 7.0 Server

    3. Program AllFusion Harvest Change Manager Agent indicates SCM 7.0 Agent

  3. There may be other eFixes/Hotfixes to above components as well

  4. Then i dentify the directory where you have installed SCM 7.0, this is referred to as %HARVESTHOME% or %CA_SCM_HOME% through out this document. This can be obtained by invoking:

    1. Windows Start -> Run -> type: cmd.exe

    2. type: set HARVESTHOME

    3. Above command would show a Directory Path, which is where SCM 7.0 was installed

    4. Default directory is: C:\Program Files\CA\AllFusion Harvest Change Manager

    5. Note down this value

    Note: If there are multiple SCM components on this host, all components get installed to the same directory.

Perform Backup:

Taking proper backup of both file systems and database is preferred incase of an un-foreseen event. This also would be useful to configure the new SCM 12.0 installation easily and close to the SCM 7.0 configuration. Below are some of the important components that need to be backed up:

  • The SCM 7.0 database. For database backup, follow your normal database backup procedures. A full (possibly a cold backup) backup of the database is preferred.

  • Entire %HARVESTHOME% directory (including subdirectories/files).

  • Any custom UDP scripts and configuration files.

  • *.arg files from %HARVESTHOME directory (HBroker.arg, HServer.arg, HAgent.arg and if present, HClient.arg)

    Make note of your backup location.

Uninstall existing SCM 7.0 components:

Next step is to uninstall existing SCM 7.0 components on each SCM 7.0 host that needs to be upgraded to SCM r12.

SCM Server Hosts:

SCM Server component should be removed using a manual uninstall process. Follow below steps:

  1. Ensure that all SCM programs (ex: Agent, Broker/Server, Client), and integrated development environments (IDEs) are shutdown/closed.


    Note: SCM Server service is usually a Windows Service under the name: Harvest Broker Service. Stop this service.

  2. Invoke Windows Start -> Control Panel -> Add/Remove Programs (If it is a Microsoft Windows XP/2003 operating system, make sure Show Updates option
    on this dialog box is checked ON to show updates/efixes/hotfixes).

  3. Select "AllFusion Harvest Change Manager Server"

  4. If there are any updates/efixes/hotfixes in this dialog box and

    1. there is a remove option available for them, remove them first by clicking on the "Remove" button.

    2. there is no remove option available for them, proceed to next step.

  5. Click the Remove option next to "AllFusion Harvest Change Manager Server".

  6. Follow further prompts to remove the component.

  7. The SCM Server component is now uninstalled.

SCM Client Hosts:

As SCM 12.0 cannot upgrade SCM 7.0 Client component, the suggestion is to remove SCM 7.0 Client and install SCM 12.0. SCM 7.0 Client component can be removed in two ways: a) Silent mode b) Manual mode. Since the Client component can exist on multiple hosts, it maybe preferred to use the silent more (ex: software delivery mechanisms). Both methods documented below.

Note: Do test the automated procedure before deploying the procedure across multiple machines.

Manual method:

  1. Ensure that all SCM programs (ex: Agent, Broker/Server, Client), and integrated development environments (IDEs) are shutdown/closed.

  2. Invoke Windows Start -> Control Panel -> Add/Remove Programs (If it is a Microsoft Windows XP/2003 operating system, make sure Show Updates option on this dialog box is checked ON to show updates/efixes/hotfixes).

  3. Select "AllFusion Harvest Change Manager Client"

  4. If there are any updates/efixes/hotfixes in this dialog box and

    1. there is a remove option available for them, remove them first by clicking on the "Remove" button.


      Note: Client Patch2/Patch4 cannot be removed. Removing SCM 7.0 Client software would remove these patches as well

    2. there is no remove option available for them, proceed to next step.

  5. Click the Remove option next to "AllFusion Harvest Change Manager Client".

  6. Follow further prompts to remove the component.

  7. The SCM Client component is now uninstalled.

Silent method:

The silent mechanism that's suggested here is to use msiexec's /X option for the SCM 7.0 Client's MSI code. So a custom wrapper/job can be pushed to SCM Client hosts with similar option and there by removing the SCM 7.0 Client software.

  • MSI code for SCM 7.0 Client is: {C53D4D51-FC1C-4CE2-898A-FB274465C66D}

  • So, to silently uninstall SCM 7.0 client, a suggested syntax that can be used is:

    msiexec /QN /X {C53D4D51-FC1C-4CE2-898A-FB274465C66D}

    Note: Additional/appropriate options of msiexec can be used based on necessity. Refer to msiexec /? for additional options.

  • Once the execution is complete, the SCM 7.0 client (including any hotfixes/eFixes) should be removed from Windows Start -> Control Panel -> Add/Remove Programs

SCM Agent Hosts:

As SCM 12.0 cannot upgrade SCM 7.0 Agent component, the suggestion is to remove SCM 7.0 Agent and install SCM 12.0. SCM 7.0 Agent component can be removed in two ways: a) Silent mode b) Manual mode. Since the Agent component can exist on multiple hosts, it maybe preferred to use the silent more (ex: software delivery mechanisms). Both methods documented below.

Note: Do test the automated procedure before deploying the procedure across multiple machines.

Manual method:

  1. Ensure that all SCM programs (ex: Agent, Broker/Server, Client), and integrated development environments (IDEs) are shutdown/closed.

    Note: SCM Agent service is usually a Windows Service under the name: Harvest Agent Service. Stop this service.

  2. Invoke Windows Start -> Control Panel -> Add/Remove Programs (If it is a Microsoft Windows XP/2003 operating system, make sure Show Updates option on this dialog box is checked ON to show updates/efixes/hotfixes).

  3. Select "AllFusion Harvest Change Manager Agent"

  4. If there are any updates/efixes/hotfixes in this dialog box and

    1. there is a remove option available for them, remove them first by clicking on the "Remove" button.

      Note: Agent Patch2/Patch4 cannot be removed. Removing SCM 7.0 Agent software would remove these patches as well

    2. there is no remove option available for them, proceed to next step.

  5. Click the Remove option next to "AllFusion Harvest Change Manager Agent".

  6. Follow further prompts to remove the component.

  7. The SCM Agent component is now uninstalled.

Silent method:

The silent mechanism that's suggested here is to use msiexec's /X option for the SCM 7.0 Agent's MSI code. So a custom wrapper/job can be pushed to Windows SCM Agent hosts with similar option and there by removing the SCM 7.0 Agent software.

  • MSI code for SCM 7.0 Agent is: {B0CDDEEE-E085-4AAF-94FD-0250ADE959BF }

  • So, to silently uninstall SCM 7.0 Agent, a suggested syntax that can be used is:

    msiexec /QN /X {B0CDDEEE-E085-4AAF-94FD-0250ADE959BF}
    Note: Additional/appropriate options of msiexec can be used based on necessity. Refer to msiexec /? for additional options.

  • Once the execution is complete, the SCM 7.0 Agent (including any hotfixes/eFixes) should be removed from Windows Start -> Control Panel -> Add/Remove Programs

Upgrading the database to SCM 7.1 standards:

Now that uninstall of the SCM 7.0 components (on the SCM Server host) is complete, next step is to upgrade the SCM 7.0 database to SCM 7.1 standard.

Follow below steps to upgrade the database:

  • Create a temporary directory for database upgrade, ex: c:\temp\71upgrade

  • Copy the file upgrade.sql (attached to this document) to c:\temp\71upgrade

  • Run upgrade.sql agains the SCM 7.0 database schema that needs to be upgraded to 7.1 standard.

    Example: sqlplus <r70_database_owner>/<r70_database_password> @upgrade.sql upgrade.log


    Note: If your database server is remote to the SCM 7.0 Server host, use the Oracle TNS Alias as well.

    Example: sqlplus <r70_database_owner>/<r70_database_password>@<Oracle_ALIAS> @upgrade.sql upgrade.log

  • Once the procedure is completed, verify upgrade.log file contents. Look for success indicators like below:

    Upgrade to R7.1 Complete
    PL/SQL procedure successfully completed.

If there are any errors and the procedure stopped, contact CA Technical Support for further analysis. Or else, the upgrade of the database is complete. Proceed to next step.

Install SCM 12.0:

Now that the database is on SCM 7.1 standards, SCM r12 software can be installed.

If you have not already done so, read the Release Notes to ensure that your DBMS version is supported for SCM 12.0. If your DBMS version does not meet the requirements listed in the Release Notes, upgrade it to a supported release before upgrading the server.

Note: You can find the most current version of the Release Notes at http://ca.com/support.

SCM Server Hosts:

To install the SCM Server software:

  • Follow the steps in CA SCM Implementation Guide -> Chapter 2 -> How to Prepare for the Server Installation

  • Either Typical/Custom option can be selected depending on the necessity (Note: Database upgrade to SCM 12.0 is done later. Not during this step).

  • After the install is complete, the "Install Wizard Completed" dialog box shows up.

  • There is an option to Launch the Database Configuration Utility.

  • Check that ON and click on Finish

  • CA SCM Change Manager Database Config Utility Window pops up.

  • Select the DBMS Type: O (for Oracle) and hit Enter key

  • Follow the instructions in CA SCM Implementation Guide -> Chapter 11 -> How to Configure the Repository using the hdbsetup Database Configuration Utility -> Upgrade the Repository (Oracle) section and Configure the ODBC DSN (Data Source Name) section.

  • Once the upgrade is complete, select the Encrypt Password option as well. This encrypts the database user credentials to the encrypted file hsvr.dfo, using the new encryption software (ETPKI).

  • Exit the Database Configuration utility and restart the machine when prompted
    Note: Restart is needed to ensure new system variables get updated.

SCM Client Hosts:

SCM 12.0 Client component can be installed in many ways. Follow the steps in CA SCM Implementation Guide -> Chapter 2 -> How to Prepare for the Client Installation.

SCM Agent Hosts:

SCM 12.0 Agent component can be installed in many ways. Follow the steps in CA SCM Implementation Guide -> Chapter 2 -> How to Prepare for the Agent Installation.

This should complete the upgrade to SCM 12.0.

Verification:

CA SCM Implementation Guide also documents Verification steps for all the above components. Follow those procedures to ensure the components are installed properly and are available for usage.

Harvest Server Versions:

If the SCM 7.0 Broker was configured with multiple Server instances, SCM 12.0 broker would have to be configured in similar way. Usually each of these Server instances connect to individual SCM databases. Each of those databases need to be upgraded to SCM 7.1 standards as well.

To identify if SCM 7.0 Broker was configured to use multiple Server instances, open %HARVESTHOME%\HBroker.arg file in your favorite text editor. Compare it with a sample HBroker.arg file from SCM 12.0 Implementation Guide -> Chapter 12 -> Broker and Server Communication -> Broker Setup for Multiple Server Instances section (page 331).

Once SCM 12.0 installation is complete, this installation needs to be reconfigured properly for the usage of multiple server instances. Refer to your backed up SCM 7.0 %HARVESTHOME% directories and SCM 12.0 Implementation Guide's Chapter 12 for this reconfiguration.

Custom Forms:

CA SCM Implementation Guide Chapter 9 documents steps involved in Form upgrades. Refer to this chapter for upgrading custom forms. Use SCM 7.0's form files as a reference and customize/create new forms in SCM 12.0.

Harweb:

Users who need to upgrade their supported application server to meet the system requirements for the new SCM 12.0 Harweb cannot use regular SCM upgrade. Instead, they must uninstall their existing Web Interface and then perform a new installation.

If a supported application server is being used, invoking Harweb's installer and selecting the Upgrade option is just enough. Refer to SCM 12.0 Implementation Guide -> Chapter 10 -> Upgrading the Web Interface section for detailed instructions of Harweb upgrade.

Contact CA Technical Support incase further questions.