Upgrade any product component from a release other than CA Harvest SCM r12.6 and r13.0.x.
Change your database.
Change the location of any component already installed, except for a network client.
Change the options for any component being upgraded, or add new options. All existing options are updated and you cannot delete them.
Upgrade the plug-in for Eclipse option.
Specify the specific components to be upgraded.

Determine whether you run the Upgrade Wizard from your local computer, a network location, or a shared drive, rather than from the installation media.
We recommend that you run the Upgrade Wizard directly from the installation media. However, if you decide not to use the installation media, verify that you have copied all of the installation files to the appropriate location and the files are accessible.
If you have not already done so, read the
Release Information
. Do not start the Upgrade Wizard until you have read that information and understand it.
Verify that you have Windows Administrator rights on the computers that you plan to upgrade.
For information about how to verify and upgrade your rights, see your Windows documentation.
Verify the accuracy of your path names.
Path names must be standard and must begin with a drive letter, such as the C:\Program Files\ or D:\somedir\someApp\.
You can use mapped drives and relative path names, such as ..\somedir\someApp.
You cannot use Universal Naming Convention (UNC) path names, such as \\myMachine\somedir\someApp.
For all supported
servers
you upgrade, complete the following steps:
Verify that the server or client of your database is on the same computer as the Database Configuration Utility. When you use the Upgrade Wizard to upgrade the server, this utility is automatically upgraded.
If applicable, verify your database administrator (DBA) credentials. If your
CA Harvest SCM
database is running locally, when you upgrade the server, enter the user name and password of the DBA (that is, the user who has administrative rights to the database tables). Therefore, have this information ready when you run the Upgrade Wizard.
Back up your database.
For information about how to back up your database, see your vendor documentation.
Back up any custom files (including UDP scripts and forms) from the %HARVESTHOME% and %HARVESTHOME%\Forms directories.
For information about how to back up custom files, see your operating system documentation.
For all
local clients
you upgrade, consider the following information:
If you already successfully ran the Upgrade Wizard on a computer, all product components are upgraded and you do not have to run the wizard again.
If you installed any options such as Windows Shell Extension, when you installed any product component, the Upgrade Wizard automatically upgrades both the component and the options to the current product release at the same time.
You cannot change existing options for a component. If you want to upgrade a component, but you also want to add an option from the current release to the component, or delete an existing option from the component, you
cannot
use the Upgrade Wizard. Uninstall the component that includes the option you do not want, and then install the component again as if you were installing it for the first time.
If you run the Upgrade Wizard on a computer that has the product's client installed, the wizard automatically installs the HSDK, JHSDK, and COM SDK while upgrading the client to the current product release.
The plug-in for Eclipse is installed and maintained separately from the product components. Therefore, if the Upgrade Wizard detects an existing version of the plug-in, the wizard upgrades all other existing product components and options,
except
for the plug-in for Eclipse.
For all
agents
you upgrade, consider the following information:
All considerations for local clients also apply to agents.
You cannot use the Upgrade Wizard to upgrade a network agent. Manually upgrade the agent.
If you use a
response file
to upgrade the product, consider the following information:
All considerations for individual product components, including the server, client (including a network client), and agent, also apply to a response file.
Remove any emergency fixes (efixes) that have been installed on the existing release.

Make sure that you have properly prepared for the upgrade.
Insert the installation media into your drive. If autorun is enabled on your computer, the Upgrade Wizard starts automatically.
If autorun is not enabled or if you are not running the upgrade from the installation media, start the wizard in Windows Explorer by double-clicking upgrade.exe in the folder where the wizard files have been copied.
The license agreement appears.
Read and accept the terms of the agreement to continue.
Review the list of product components already installed.
If your computer has any product components installed that you do
not
want to upgrade, exit the wizard now. Then, uninstall the components and install the component again as if you were installing it for the first time.
Click Upgrade to start the upgrade.
If prompted, select the location where your computer can access the product installation files for the component being upgraded. Browse to the location and click OK.
Typically, if the wizard prompts you for the location of the installation files for the product components, you are prompted in the following order: agent, client, and server.
Continue entering the requested locations for all product components.
Continue following the on-screen instructions to complete the upgrade.

Copy the default Upgrade Wizard response file (DHUR021705.rkr) to the location from where the upgrade will be run.
The DHUR021705.rkr file is provided on the installation media in the \upgrade folder.
Use a text editor to open the DHUR021705.rkr file and read the terms of the license agreement.
Accept the terms of the license agreement, as follows:
Find the license agreement parameter listed in the text of the agreement.
Enter the license agreement parameter as an executable option in the file and save the file.
If you do not accept the license agreement terms, the upgrade will not work.
Enter the -silent option either as a parameter in the DHUR021705.rkr file or enter it on the command line.
(Optional) Modify the response file parameters in the DHUR021705.rkr file based on your specific requirements.
If any option is needed for the upgrade but is not supplied in the response file, the user running the upgrade is prompted to enter the required values. For example, if the upgrade detects that the client is installed and needs to be upgraded, the upgrade checks for the corresponding entry (-clinstloc=
client-install-path-name
) in the response file. If this entry does not exist in the response file, the upgrade uninstalls the previous client and then prompts the user running the upgrade for the location of the new client installation files.
From the command line, enter the following command:
 
upgrade -response="pathname\DHUR021705.rkr" -silent 
pathname
Specifies the complete path name or relative path name to the response file DHUR021705.rkr.
If any part of the
path name
in this command includes a space, enclose the complete path name in quotation marks. For example, enclose the path name in -response=”c:\my files\temp\hupgrade.exe” in quotation marks.
The following sample command illustrates a complete path name.
 
"C:\Program Files\CA\SCM" 
The following sample command illustrates a relative path name.
 
"..\CA\SCM" 
-silent
Specifies that the response file executes silently, with no user input or notification.
Use the hdbsetup Database Configuration Utility to upgrade the database.

 
-svinstloc=server-install-pathname 

 
-svinstloc="server-install-pathname" 

-svinstloc=server-install-path-name
Specifies the path name of the installation files for the server.
-clinstloc=client-install-path-name
Specifies the path name of the installation files for the client.
-aginstloc=agent-install-path-name
Specifies the path name of the installation files for the agent.
-scmagentport=<
portnumber
>
Specifies the port number for the agent components.
-vciinstloc=vsip-install-path-name
Specifies the path name of the installation files for Visual Studio Plug-in.

 
convpw -db DBResource DBUsername DBPassword 
convpw -dfo 
convpw -dfo filenamec