CA Harvest SCM 14.0

PDF
14.0 13.0
English

Upgrade on UNIX, Linux, and zLinux

This article details about you can upgrade your  on UNIX, Linuz, and z/Linux.
cahscm140
This article details about you can upgrade your
CA Harvest SCM
 on UNIX, Linuz, and z/Linux.
2
Prepare for the Server Upgrade
An
upgrade
means that you install the latest
CA Harvest SCM
 Release server software, and then you upgrade the database.
If you specify CA_SCM_HOME to the existing install directory for the installation of the
CA Harvest SCM
 Release r12.6 or v13.x server, the following actions automatically occur:
  • arg files are updated.
  • existing dfo files are converted to eTPKI format.
If you install
CA Harvest SCM
 Version 14.0 to a separate directory, you must run svrenc to encrypt the passwords for the server, LDAP, and user-defined dfo files in the CA_SCM_HOME directory.
Follow these steps:
  1. Back up your database.
    For information about how to back up your database, see your vendor documentation.
  2. Back up any custom files (including custom UDP scripts and custom forms) from the $HARVESTHOME and $HARVESTHOME \forms directories if you are installing to the same location as the previous installation.
    For information about how to back up custom files, see your operating system documentation.
  3. Install or upgrade the Public Key Infrastructure (eTPKI).
  4. Install or upgrade PEC.
  5. Install or upgrade ODBC.
Extract the Installation Files
Complete these steps before performing an upgrade.
Do the following before you start these steps:
  • On Linux, verify that the umask is set to 0022.
  • On UNIX, verify that the umask is set to 022.
  • Log on as the
    cascm
    user (the user named
    cascm
    ).
  • Insert the installation media for your UNIX or Linux operating environment into the drive. Mount the drive if necessary. The following instructions use /cdrom as the mount point.
  • Change to the installation directory. For example, if you are using the default installation directory, enter the following command:
     
    cd /opt/CA/scm
  • Enter the following command to copy the installation files for your UNIX or Linux operating environment to the current directory. Verify that you include the space and period at the end of the command; they represent the current directory.
     
    cp /cdrom/bin/directory/scm.tar.gz
    • directory
      Specifies the directory for your UNIX or Linux operating environment.
  • (AIX operating environments only) As the root user, run slibclean to clear all cached lib executables so that the lib files are available for overwrite during the extraction process.
  • Enter the following commands to extract the files:
     
    gunzip scm.tar.gz
     
    tar xvf scm.tar
    The installation files are extracted.
Upgrade a Server (Local and Remote Oracle Database)
You can
upgrade
 a
CA Harvest SCM
 release r12.6 or v13.x server running a local or remote Oracle database to the current release of the product. After extracting and installing the tar files, perform the following steps to upgrade the server.
r7.1 upgrade to V13.0.3 64-bit Non-Windows server:
To upgrade from r7.1 to V13.0.3, you must upgrade the r7.1 server to r12.6 32-bit server and then,  proceed to upgrade to V14 64-bit server.
Example:
 r7.1 Linux 32 bit Server ---> r12.6 Linux 32bit Server ---> V14.0 Linux 64-bit Server
As there is no 64-bit support for 7.1 installation, during upgrade process you must upgrade to  32-bit installation of r12.5 and then upgrade to the 64 bit installation of V14.0
Before you begin, verify that the product broker, server, and agent processes are not running.
Follow these steps:
  1. After extracting the Version 14.0 tar files, navigate to the product installation directory. For example, enter the following command:
     
    cd /opt/CA/scm/install
  2. Enter the following command to run the installation script:
     
    ./install.sh
  3. From the installation options, select option [2] Upgrade SCM. This option upgrades the product from release 12.x to the current release.
  4. Specify the method the product server and agent will use to authenticate users' logon credentials.
    • Internal
      Uses internal (
      CA Harvest SCM
      ) authentication. Login credentials provided to the broker are validated against the internal product user data.
      If you select Internal, skip the rest of this step and continue at the next step.
    • OpenLDAP
      Uses an external server. Login credentials provided to the broker are validated against the external authentication server. If you select OpenLDAP authentication, you are prompted to supply the required LDAP-related information. These required LDAP values and optional values appear in confirmation pages so that you can verify them. Optional fields are automatically filled with default values. You can change them in the confirmation pages as needed.
      For details about these fields, see LDAP Compliant Directory Configuration Parameters.
      When you install LDAP authentication, the OpenLDAP and OpenSSL open source libraries are installed automatically in the product folders, if they are not already installed. For information about OpenLDAP, see the OpenLDAP web site. For information about OpenSSL, see the OpenSSL web site.
    • Mixed Mode authentication
      Lets the SCMAdmin create users internally even though the authentication mode may be set to External (LDAP).
      Mixed Mode authentication does not use LDAPserver for Authentication if users are created internally.
    • External User Group authentication
      Lets the SCMAdmin define LDAP support for external user groups.
  5. Specify that you are using an Oracle database.
  6. The values for CA_SCM_HOME and DBMS-related environment variables appear. When prompted, select the appropriate number to modify a value; otherwise, accept the default [0] to continue.
  7. If the eTrust Public Key Infrastructure (CAPKI) location is not available you may be prompted to enter the path to the CAPKI installation directory. If prompted, enter the complete path to the eTPKI installation directory. If not prompted, go to the next step.
  8. If RTHOME is not set, you are prompted to enter the Enterprise Communicator (PEC) installation directory. If you are not prompted, the installation uses the current value of the environment variable, $RTHOME. If prompted, enter the Enterprise Communicator installation directory; the default is /opt/CA/pec.
  9. To run the product server from behind a firewall, you must specify a range of available ports, as follows:
    At the Firewall port range prompt, specify the port range by entering the starting port number, a comma, and the ending port number. (Spaces are optional and are ignored.) For example, to specify a port range of 1500 through 1502, enter the following at the prompt:
     
    1500, 1502
    The number of ports in the range must be greater than or equal to the maximum number of server processes and remote agents running behind the firewall.
  10. The Database Configuration Utility (hdbsetup) starts. Use this utility to configure your database. This utility helps you to upgrade the database schema but does not remove or overwrite existing product data. You can optionally run the utility now or later, but you must run the utility before you can start using the product.
    If you are using Oracle, do not use configdsn to set up your
    CA Harvest SCM
     database. You must use the Database Configuration Utility instead.
    Check the $CA_SCM_HOME/install/log directory for log files created during the upgrade.
    After the installation is complete, if you backed up custom files including UDP scripts and forms from your previous installation, copy these files back to the %CA_SCM_HOME% and %CA_SCM_HOME%\forms directories.
Upgrade the Command-line utilities
You upgrade the
CA Harvest SCM
 command-line utilities so you can use the new product features.
To upgrade the command-line utilities, do
one
of the following:
  • Make the files in $HARVESTHOME writable and install the new version of the command line utilitiescommand-line utilitiesas the existing version.
    You need to regenerate the .dfo files if any exist for using the svrenc utility.
  • Delete the existing version of the command-line utilities and then install the new version in the new location.
The command-line utilities are upgraded.
Back up all custom files from %HARVESTHOME% and %HARVESTHOME%\forms directories. Make note of your backup location.
Upgrade the Agent
You upgrade the
CA Harvest SCM
 agent so you can use the new product features.
If you are upgrading from a previous release and you are running the agents on
remote
computers, you must install the agents on the remote computers. If the agents are already installed, follow this step.
To upgrade the agent, do
one
of the following:
  • Make the files in $CA_SCM_HOME writable and install the new version of the agent in the same location as the existing version.
    You need to regenerate the .dfo files if any exist for using the svrenc utility.
  • Delete the existing version of the agent and then install the new version in the new location.
The agent is upgraded.