CA Harvest Change Manager r71 Patch 2 Readme - CA Technologies
{{search ? 'Close':'Search'}}

CA Harvest Change Manager r7.1 Patch 2 Readme

1.0 Welcome

2.0 See the Harvest r7.1 Readme

3.0 Installation Instructions
3.1 Install Database Patch Harvest r7.1 Patch 2 Server on Windows
3.2 Install Harvest r7.1 Patch 2 on Windows Local Computers
3.3 Install Harvest r7.1 Patch 2 on Windows Network Computers
3.4 Install Database Patch Harvest r7.1 Patch 2 Server on Unix/Linux
3.5 Install Harvest r7.1 Patch 2 on UNIX or Linux
3.6 Roll Back Harvest r7.1 Patch 2 on UNIX or Linux
3.7 Install Harvest r7.1 Patch 2 on z/OS
3.8 Back up Harweb on Windows, UNIX or Linux
3.9 Install Harweb r7.1 Patch 2 on Windows, UNIX, or Linux
3.10 Roll Back Harweb r7.1 Patch 2 on Windows, UNIX or Linux

4.0 Published Fixes

5.0 Known Issues

6.0 Downloads

7.0 Contact Technical Support


1.0 Welcome

Welcome to CA Harvest Change Manager r7.1 Patch 2 (Harvest). This readme contains instructions to install and set up CA Harvest r7.1 Patch 2, including CA Harvest Change Manager Web Interface (Harweb).


2.0 See the Harvest r7.1 Readme

For operating system support, system requirements, known issues, installation considerations, general considerations, and related information for Harvest r7.1, see the Harvest r7.1 readme. The Harvest r7.1 Patch 2 readme (this file) covers only information that is unique to the patch. For instructions to install Harvest r7.1, see the Harvest r7.1 Installation Guide. All Harvest documents are available in the Docs directory on the Harvest r7.1 installation media. For the latest versions of these documents, see Technical Support at http://ca.com/support.


3.0 Installation Instructions

Important! On all platforms, for any Harvest component except Harweb, to install Harvest r7.1 Patch 2 successfully, you must have an existing Harvest r7.1 version of the component already installed!

However, from the Harvest r7.1 Patch 2 installation media, on all platforms, you can install a new version of Harweb or upgrade an existing Harweb r7.1 version.

Note: Harvest r7.1 Patch 2 is cumulative; that is, Patch 2 includes all fixes that were in eFixes after Harvest r7.1 GA was shipped to manufacturing.


3.1 Install Database Patch Harvest r7.1 Patch 2 Server on Windows

Important: Harvest r7.1 Patch 2 requires a database update with Microsoft SQL Server and Ingres for performance improvements. This patch must be installed on your Harvest database by your database administrator.

To install the MDB Patch on Windows servers:

Note: When updating the MDB on Microsoft SQL Server using Windows Authentication, the Windows user account used to run the database script requires the "sysadmin" role.

For SQL Server:

1. Open a command prompt window.

2. Execute the following commands:

  • cd %harvesthome%DatabaseSQL ServerCumulativePatch

  • PatchMDB.bat -DBMS_INSTANCE=local -MDB_NAME=mdb -MDB_PATCH=15089641

    For Ingres:

    1. Open a command prompt window.

    2. Execute the following commands:

  • cd %harvesthome%DatabaseMDBmdb15089641

  • PatchMDB.bat -II_MDB_NAME=mdb -II_MDB_PATCH=15089641

  • %harvesthome%DatabaseHarvest_Ingres_MDB_Maintenance.bat

    For Oracle

    There is no database change required.


    3.2 Install Harvest r7.1 Patch 2 on Windows Local Computers

    Important! For the Windows Server, Harvest r7.1 Patch 2 has been superceded by Harvest r7.1 Patch 2 + Hot Fix 1. The Harvest r7.1 Patch 2 + Hot Fix 1 Server installation media contains all fixes in Patch 2 plus an addtional critical fix to the server for VCI and Eclipse.

    If you have the Harvest Client and/or Agents installed on the same machine as the Harvest server, AND you have previously applied any eFixes or Hot Fixes for Patch 2 to the Client OR Agent, you will need to reapply those Hot Fixes.

    Harvest r7.1 Patch 2 + Hot Fix 1 requires that you uninstall Patch 2 before the new installation media will procede.

    For local installations on Windows, Harvest r7.1 Patch 2 is supplied in these files, for the Harvest server, client, and agent, respectively:

  • Har71Patch2Hotfix1Server.exe

  • Har7.1Patch2Client.exe

  • Har7.1Patch2Agent.exe

    To install Harvest r7.1 Patch 2 on Windows on a local computer

  • Close all Windows applications except Windows Explorer. Ensure that you close any IDE programs.

  • Ensure that the patch files are accessible to all Harvest server, client, and agent computers. For example, you can copy the files to a network drive, CD, or local computer and run them from any of those locations.

  • In Windows Explorer, open the folder containing the Harvest r7.1 Patch 2 files.

  • Run the matching Har7.1Patch2*.exe file for the Harvest r7.1 component or components installed, as follows:

  • On Harvest server computers, run Har71Patch2Hotfix1Server.exe

  • On Harvest client computers, run Har7.1Patch2Client.exe

  • On Harvest agent computers, run Har7.1Patch2Agent.exe

    Important! If you have one or more Harvest r7.1 components installed on a computer, run the matching Harvest r7.1 Patch 2 file for each installed component. For example, if a computer has both the Harvest r7.1 server and agent installed, run both Har7.1Patch2Server.exe and Har7.1Patch2Agent.exe on that computer.

    On computers with multiple Harvest r7.1 components, the order in which you run the patches is not important. However, you must update all Harvest r7.1 components on a computer with the patch before you can use Harvest again on that computer.


    3.3 Install Harvest r7.1 Patch 2 on Windows Network Computers

    For network installations on Windows, Harvest r7.1 Patch 2 is supplied in these files, for the shared Harvest client and agent, respectively:

  • Har7.1Patch2Client.exe

  • Har7.1Patch2Agent.exe

    For background information about installing shared Harvest clients and agents on a network, see the chapters "Upgrading or Installing the Harvest Client on Windows" and "Upgrading or Installing the Harvest Agent on Windows" in the Harvest r7.1 Installation Guide.

    Important! Rolling back Harvest r7.1 Patch 2 is not supported on Windows; therefore, before running the patch, ensure that you want to upgrade!

    To install Harvest r7.1 Patch 2 on a shared Harvest client or agent on a Windows network computer

  • Uninstall the Harvest r7.1 client (or agent) on all network computers.

  • On the network server computer that hosts the shared Harvest client or agent, copy the existing Harvest r7.1 administrative image (the existing Harvest r7.1 administrative installation files and directories).

    Note: The backup will be useful if you need to uninstall Harvest on any network computer after the existing administrative image is updated to Harvest r7.1 Patch 2.

  • Apply the patch to the administrative image of the shared Harvest client by running the following command at the command prompt on the network server computer:
     Har7.1Patch2Client.exe /v"/a "pathnameCA Software Change Manager Client.msi"" 

    pathname
    Specifies the complete path name of the administrative image for the shared Harvest client network installation.

    For example, if the path name of the image is c:Harvest7Client, enter the following command:
     Har7.1Patch2Client.exe /v"/a "c:Harvest7ClientCA Software Change Manager Client.msi"" 

  • Apply the patch to the administrative image of the shared Harvest agent by running the following command at the command prompt on the network server computer:
     Har7.1Patch2Agent.exe /v"/a "pathnameCA Software Change Manager Agent.msi"" 

    pathname
    Specifies the complete path name of the administrative image for the shared Harvest agent network installation.

    For example, if the path name of the image is c:Harvest7Client, enter the following command:
     Har7.1Patch2Agent.exe /v"/a "c:Harvest7AgentCA Software Change Manager Agent.msi"" 

  • Re-install the Harvest r7.1 client or agent on all network computers, using the patched administrative images for Harvest r7.1 Patch 2 that you created in the previous steps, not the administrative images from Harvest r7.1 GA. For instructions, see the chapters "Upgrading or Installing the Harvest Client on Windows" and "Upgrading or Installing the Harvest Agent on Windows" in the Harvest r7.1 Installation Guide.


    3.4 Install Database Patch Harvest r7.1 Patch 2 Server on Unix/Linux

    To install the MDB Patch on Unix/Linux servers:

    For Ingres:

    1. Open a shell window.

    2. Execute the following commands:

  • cd %harvesthome%/Database/MDB/mdb15089641

  • PatchMDB -II_MDB_NAME=mdb -II_MDB_PATCH=15089641

  • %harvesthome%/Database/Harvest_Ingres_MDB_Maintenance.batshesthomeDatabaseMDBmdb15089641

    For Oracle

    There is no database change required.


    3.5 Install Harvest r7.1 Patch 2 on UNIX or Linux

    On UNIX and Linux, Harvest r7.1 Patch 2 is supplied in one file, HARR7.1PATCHnumber-platform.tar.gz.

    number
    Specifies the number of the patch, for example, 002 for Patch 2.

    platform
    Specifies the operating system. Valid values are AIX, HPUX, LINUX, and SUN.

    Note: In these steps, do not enter the dash (-) in number-platform literally. The dash is used this way in these steps only to separate the number and platform variables so that they are easier to read. A sample file name is HARR7.1PATCH002LINUX.tar.gz.

    The HARR7.1PATCHnumber-platform.tar.gz file includes updates for all Harvest components, including the Harvest server, client, and agent. This file also includes updates for CAI/PT ODBC.

    Important! If you are upgrading your Harvest server to Harvest r7.1 Patch 2, you must also upgrade CAI/PT ODBC manually, as explained in the following steps.

    To install Harvest r7.1 Patch 2 on UNIX or Linux, follow these steps:

  • On Linux, ensure that the umask is set to 0022. On UNIX, ensure that the umask is set to 022.

  • Log on to the operating system using your UNIX or Linux Harvest account.

  • Close all Harvest client applications.

  • If this computer is a Harvest server, shut down the Harvest broker and all Harvest server processes.

  • If the $HARVESTHOME/PATCHES directory does not exist, create it.

  • Copy the HARR7.1PATCHnumber-platform.tar.gz file to the $HARVESTHOME/PATCHES directory.

  • Change the current directory to $HARVESTHOME/PATCHES.

  • Enter the following command to decompress the file:
     gzip –d HARR7.1PATCHnumber-platform.tar.gz 

  • Enter the following command to un-tar the file:
     tar xvfo HARR7.1PATCHnumber-platform.tar 

    This step creates the $HARVESTHOME/PATCHES/HARR7.1PATCHnumber directory, if it does not already exist.

  • If you have previously executed this patch, rename or remove any previous backup directory for this patch.

  • If you are not upgrading your Harvest server, skip this step and continue at the next step.

    If you are upgrading your Harvest server, locate the odbc311.tar.gz file in $HARVESTHOME/PATCHES/HARR7.1PATCHnumber directory. Using this file, install or upgrade CAI/PT ODBC; for instructions, see the chapter "Upgrading or Installing the Harvest Server on UNIX and Linux" in the Harvest r7.1 Installation Guide.

    Note: When installing or upgrading CAI/PT ODBC, ensure that you use this updated version of odbc311.tar.gz file (from Harvest r7.1 Patch 2), not the original version (from Harvest r7.1 GA).

  • Change the current directory to the $HARVESTHOME/PATCHES/HARR7.1PATCHnumber directory.

  • Enter the following command:
     ApplyPATCH.sh 

  • Review the PATCH.log file in the $HARVESTHOME/PATCHES/HARR7.1PATCHnumber_BKP directory.


    3.6 Roll Back Harvest r7.1 Patch 2 on UNIX or Linux

    To roll back (uninstall) Harvest r7.1 Patch 2 on UNIX or Linux, follow these steps:

  • On Linux, ensure that the umask is set to 0022. On UNIX, ensure that the umask is set to 022.

  • Log on to the operating system using your UNIX or Linux Harvest account.

  • Close all Harvest client applications.

  • If the computer on which you are installing the patch is a Harvest server, shut down the Harvest broker and all Harvest server processes.

  • Change the current directory to the $HARVESTHOME/PATCHES/HARR7.1PATCHnumber_BKP directory.

  • Enter the following command to run the rollback file:
     RollbackUPDATE.sh 

  • Review the PATCH.log file in the $HARVESTHOME/PATCHES/HARR7.1PATCHnumber_BKP directory.

    Note: Rolling back the patch does not remove the backup directory. To remove that directory, delete it manually.


    3.7 Install Harvest r7.1 Patch 2 on z/OS

    Harvest r7.1 Patch 2 includes an updated z/OS Agent and ISPF client. The updated ISPF client includes a new load library with ISPF interface executables. To install Harvest r7.1 Patch 2 on z/OS, apply the patch to the z/OS agent and the ISPF client, as follows:

    To install Harvest r7.1 Patch 2 for the z/OS agent

  • Rename the current z/OS agent installation directory.

  • Follow the instructions in the CA Software Change Manager Installation Guide for installing the z/OS agent; however, instead of using the agentonly.tar file from the Harvest r7.1 GA installation CD, use the agentonly.tar file included with Harvest r7.1 Patch 2.

    To install Harvest r7.1 Patch 2 for the ISPF client

  • Rename the existing Harvest r7.1 partition data sets (PDS) and load libraries.

  • Follow the instructions in the CA Software Change Manager Installation Guide for installing the ISPF client; however, instead of using the unload data set from the Harvest r7.1 GA installation CD, use the unload data set included with Harvest r7.1 Patch 2.


    3.8 Back up Harweb on Windows, UNIX or Linux

    Running Harweb r7.1 Patch 2 does not back up your existing Harweb r7.1 files. Therefore, back up those files manually before you run the patch. This backup is required if you need to roll back Harweb r7.1 Patch 2! To back up your Harweb r7.1 files, follow these steps:

  • Identify the Harweb deployment directory in your web application server. The default Harweb deployment directories are:

    For Sun Java System Web Server:
     SunOne_Homehttp-server-namewebapps http-server-nameharweb 

    For Apache Tomcat:
     CATALINA_HOMEwebappsharweb 

    For WebSphere Application Server:
     ..WebSphereAppServerinstalledAppscomputer-nameharweb.earharweb.war 

  • To back up Harweb on Windows, enter the following command:
     xcopy /E /K /Y /I harweb-deploy-directory backup-directory 

    To back up Harweb on UNIX or Linux, enter the following command:
     cp –r harweb-deploy-directory backup-directory 


    3.9 Install Harweb r7.1 Patch 2 on Windows, UNIX, or Linux

    On UNIX and Linux, Harweb r7.1 Patch 2 is supplied in one file named HPT.tar.

    On Windows, Harweb r7.1 Patch 2 is supplied in one file HPT.zip.

    Important! Running Harweb r7.1 Patch 2 does not back up your existing Harweb r7.1 files. Therefore, back up those files manually before you run the patch. For instructions to back up your existing Harweb r7.1 files, see the previous section, Backing up Harweb on Windows, UNIX, or Linux. This backup is required if you need to roll back Harweb r7.1 Patch 2!

    You can use Harweb r7.1 Patch 2 for both new installations and upgrades of Harweb, as follows:

  • Install new Harweb will install a new Harweb to r7.1 Patch 2 version without the requirement of install Harweb r7.1 GA version.

  • Upgrade Harweb will upgrade existing Harweb r7.1 GA version to r7.1 Patch 2.

    Note: Harweb r7.1 Patch 2 adds the ability to upgrade Harweb running on the JBoss Application server.

    For detail on how to install or upgrade Harweb, see the Harvest r7.1 Installation Guide. The Harweb r7.1 installation files mentioned in that guide are also included in the Harweb r7.1 Patch 2 files: HPT.tar on UNIX and Linux and HPT.zip on Windows.

    To run Harweb r7.1 Patch 2 on UNIX or Linux, follow these steps:

  • Log in to the operating system using your UNIX Harweb account.

  • If you plan to upgrade an existing Harweb installation, back up its files. For instructions, see the previous section, Backing up Harweb on Windows, UNIX or Linux.

  • To copy the HPT.tar file to a temporary directory, enter the following command:
     tar xvf HPT.tar 

  • Ensure that these files are extracted: HarwebInstall.sh, HarwebInstall.jar, and harweb.war.

  • Follow the instructions for upgrading or installing Harweb in the Harvest r7.1 Installation Guide, using the files you extracted in the previous step instead of the Harweb files supplied on the Harweb r7.1 GA installation CD.

    To install or upgrade Harweb r7.1 Patch 2 on Windows, follow these steps:

  • Log in to the operating system using your Windows Harweb account.

  • If you plan to upgrade an existing Harweb installation, back up its files. For instructions, see the previous section, Backing up Harweb on Windows, UNIX or Linux.

  • To copy the HPT.zip file to a temporary directory, enter the following command:
     unzip HPT.zip 

  • Ensure that these files are extracted: HarwebInstall.sh, HarwebInstall.jar, and harweb.war.

  • Follow the instructions for upgrading or installing Harweb in the Harvest r7.1 Installation Guide, using the files you extracted in the previous step instead of the Harweb files supplied on the Harweb r7.1 GA installation CD.


    3.10 Roll Back Harweb r7.1 Patch 2 on Windows, UNIX or Linux

    Important! To roll back Harweb r7.1 Patch 2, you must have backed up your existing Harweb r7.1 files manually before you ran the patch! For instructions to back up your existing Harweb r7.1 files, see the previous section, Backing up Harweb on Windows, UNIX, or Linux. If you did not perform this backup, you cannot roll back Harweb r7.1 Patch 2!

    To roll back Harweb r7.1 Patch 2, follow these steps:

  • Identify the Harweb deployment directory in your web application server. The default Harweb deployment directories are:

    For Apache Tomcat:
     CATALINA_HOMEwebappsharweb 

    For JBoss Application Server:

    If you specified during installation to deploy all JBoss services (JBOSSCONFIGURATION=all), copy harweb.war to %JBOSS_HOME%/server/all/deploy.

    If you specified during installation to deploy the default JBoss services only (JBOSSCONFIGURATION=default), copy harweb.war to %JBOSS_HOME%/server/default/deploy.

    For Sun Java System Web Server:
     SunOne_Homehttp-server-namewebapps http-server-nameharweb 

    For IBM WebSphere Application Server:
     ..WebSphereAppServerinstalledAppscomputer-nameharweb.earharweb.war 

  • Delete the Harweb r7.1 Patch 2 deployment directory identified in Step 1.

  • Roll back the Harweb backup. To backup Harweb, do the following command:

  • On Windows, to revert to your backup version of Harweb r7.1, enter the following command:
     xcopy /E /K /Y /I backup-directory harweb-deploy-directory 

    On UNIX or Linux, to revert to your backup version of Harweb r7.1, enter the following command:
     cp –r backup-directory harweb-deploy-directory 


    4.0 Published Fixes

    For a list of published fixes in Harvest r7.1 Patch 2, see the List of Published Fixes for Harvest r7.1.


    5.0 Known Issues

    PR5744: In Microsoft Visual Studio 2005, when you add a new web site to Harvest, using the Add Website to Source Control operation, the web site is added to the /root/website directory of the Harvest repository, instead of the correct location, /root/solution/website. All items and files for the new web site are then added to the /root/website directory. As a result, Visual Studio 2005 and Harvest may become unsynchronized when you add another new web site to the same repository.

    This problem occurs because of a bug in Visual Studio 2005. As a work-around, when you use the Harvest View Path dialog to add a new web site to the repository, do one of the following:

  • Select the Show Solution option, select the solution, and then select File, Source Control, Add Solution to Source Control. Verify that the view path is /root/solution/website.

  • Select the context and explicitly create the view path /root/solution/website.

    Rolling Back Patch 2 on Windows Server 2003

    You will not be able to rollback/uninstall Harvest r7.1 Patch 2 on Windows Server 2003 version prior to Windows Server 2003 SP1.

    In order to remove Harvest r7.1 Patch 1 or Patch 2 on the GA release of Windows Server 2003, you must completely uninstall Harvest.

    Starting with Windows Server 2003 SP1, the ability to uninstall just the patch has been enabled on the operating system.


    6.0 Downloads

    CA Software Change Manager r7.1 patches are available as separate downloads for Windows, UNIX and Linux:

    Apply the HARVEST patch to all Harvest Installations. On Windows apply the Client, Server, or Agent patches where those components are installed in your environment.

    Apply the HARVEST and HARWEB patch to the Harweb Installation on UNIX and Linux. On Windows, you must install the Client patch and the HARWEB Patch.

    Product Operating System - File Size
    README
    (Harvest & Harweb)
    HTML - 26 KB TEXT - 20 KB          
    HARVEST Windows Client - 30.3 MB

    Windows Server - 16.9 MB
        ISScript11.Msi
        (Required)

    Windows Agent - 9.48 MB
    Solaris - 17.5 MB AIX - 53.4 MB HP-UX - 25.5 MB HP-Itanium - 43.0 MB Linux x86 (SUSE, Redhat) - 18.8 MB SuSE Linux s390 - 16.3 MB
    HARWEB Windows - 96.4 MB Unix - 96.5 MB          

    CA Software Change Manager r7 MVS and USS agent downloads are available below:

    MVS/USS Agent
    agentonly.tar - 33.2 MB
    reload - 13 KB
    unload - 34.4 MB


    7.0 Contact Technical Support

    For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Technical Support at http://ca.com/support.

  • HARVEST - Harvest Client (GUI, CLI), Server, Agent, Windows Shell Ext, VCI, SDK, Eclipse Plugin

  • HARWEB - Harweb

Chat with CA

Just give us some brief information and we'll connect you to the right CA Expert.

Our hours of availability are 8AM - 5PM CST.

All Fields Required

connecting

We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile


  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.


    How Did We Do?
    Let us know how we did so that we can maintain a quality experience.

    Take Our Survey >

    Rate Your Chat Experience.

    {{chat.statusMsg}}

agent is typing