CA Software Change Manager Release 521 Patch 3 Readme E000134-2E - CA Technologies
{{search ? 'Close':'Search'}}

CA Software Change Manager Release 5.2.1 Patch 3
E000134-2E

Last Updated: October 15, 2004


1.0 Welcome

2.0 Operating System Support
2.1 Windows
2.2 UNIX
2.3 Linux
2.4 z/OS

3.0 System Requirements
3.1 Windows
3.2 UNIX and Linux
3.3 SuSE Linux s/390
3.4 z/OS
3.5 WebSphere Studio Integration (WSAD Integration)
3.6 TestDirector Integration
3.7 Version Control Integration (VCI)

4.0 Installation Considerations
4.1 Installing Harvest Release 5.2.1 Patch 3 on Windows
4.2 Rolling Back (Uninstalling) Harvest Release 5.2.1 Patch 3 on Windows
4.3 Installing Harvest Release 5.2.1 Patch 3 on UNIX or Linux
4.4 Rolling Back (Uninstalling) Harvest Release 5.2.1 Patch 3 on UNIX or Linux
4.5 Installing Harweb Release 5.2.1 Patch 3 on UNIX or Linux
4.6 Rolling Back (Uninstalling) Harweb Release 5.2.1 Patch 3 on UNIX or Linux
4.7 Running the Database Upgrade Patch
4.8 Changing Item Access Process to GRANT
4.9 Miscellaneous

5.0 General Considerations

6.0 List of Fixes
6.1 Harvest Release 5.2.1 Patch 2 Fixes
6.2 Harvest Release 5.2.1 Patch 3 Fixes

7.0 Known Issues
7.1 Access Control
7.2 Agent Connection Problems
7.3 Agent Modes
7.4 Agent Shutdown
7.5 Check In and Check Out
7.6 Command Line
7.7 Form Management
7.8 Graphical User Interface
7.9 Harweb
7.10 Installation
7.11 Illegal Characters
7.12 Linux
7.13 Password Policy
7.14 Security Concerns
7.15 Version Control Interface (VCI)
7.16 WebSphere Studio Integration (WSAD Integration)
7.17 Direct Connect Considerations

8.0 Language Certifications

9.0 Documentation

10.0 Contacting Technical Support

11.0 Downloads


1.0 Welcome

Welcome to CA Software Change Manager Release 5.2.1 Patch 3. (CA Software Change Manager is hereafter called Harvest.) This readme file contains installation considerations, operating system support, known issues, and instructions for contacting Computer Associates Technical Support.

This readme covers all standard and optional components for Harvest Release 5.2.1:

  • The Harvest server, client, agent, and command line utility

  • The Harvest SDK components: the Harvest SDK (HSDK), the Java Harvest SDK (JHSDK), and the Component Object Model SDK (COM SDK). In previous Harvest releases, SDK components were sold separately.

  • CA Software Change Manager Web Interface (hereafter called Harweb)

  • CA Software Change Manager WebSphere Studio Integration (hereafter called WebSphere Studio Integration) also called WSAD Integration

  • CA Software Change Manager TestDirector Integration (hereafter called TestDirector Integration)

  • CA Software Change Manager Version Control Interface (hereafter called VCI)

    Note: For information about CA Software Change Manager Custom Reports, see the readme file (readme_samplereports.html or readme_samplereports.txt) on the CA Software Change Manager Release 5.2.1 Custom Reports CD.


    2.0 Operating System Support

    This section lists the operating systems supported by Harvest Release 5.2.1 components. Computer Associates supports each operating system for the duration of its life cycle (as determined by its manufacturer) or until Computer Associates announces that we are dropping support for it. For the latest information about supported operating systems, see our web site, SupportCA.


    2.1 Windows

    This section lists the Windows operating systems supported by Harvest Release 5.2.1 components.

    The Harvest server, Harvest client, Harweb, WebSphere Studio Integration (WSAD Integration), Version Control Interface (VCI), and TestDirector Client require one of the following operating systems:

  • Windows 2000 Server

  • Windows 2000 Advanced Server

  • Windows Server 2003 Enterprise

  • Windows XP Professional

    TestDirector server requires one of the following:

  • Windows 2000 Server

  • Windows Server 2003 Enterprise

    Harweb requires an operating system that supports one of the following web browsers:

  • Microsoft Internet Explorer 6.0

  • Mozilla 1.4 to 1.7


    2.2 UNIX

    This section lists the UNIX operating systems supported by Harvest Release 5.2.1 components.

    The Harvest server on UNIX requires one of the following:

  • Sun Solaris 2.7, 2.8, or 2.9

  • HP-UX 11.00 or 11.11 (11i)

  • IBM AIX 4.3.3, 5.1, or 5.2

    Harweb on UNIX requires one of the following:

  • Sun Solaris 2.7, 2.8, or 2.9

  • IBM AIX 4.3.3, 5.1, or 5.2

  • HP-UX 11.00 or 11.11

    The HSDK on Sun Solaris runs on Solaris 2.6, 2.7, or 2.8 systems.

    Note: If you are using Solaris 2.8 and the Sun Workshop compiler 5 and Forte 6, you must do the following:

  • Set the flag -compat=4 in the compile stream.

  • In the cacheckin.h and cacheckout.h files, you must replace the following statement:
     #if defined(__hpux) 

    with this statement:
     #if defined(__hpux) || ( __SUNPRO_CC >= 0x500 ) 

    The HSDK on AIX requires AIX 4.3.3 and IBM CXX compiler 3.6.6.

    The HSDK on HP-UX requires HP-UX 11.00 and HP aCC compiler A.03.25 or higher.


    2.3 Linux

    This section lists the Linux operating systems supported by Harvest Release 5.2.1 components.

    The Harvest server on Linux requires one of the following:

  • Red Hat Advanced Server 3.0. To work properly with Harvest, Red Hat Advanced Server 3.0 requires that you install the latest applicable ODBC311 patch available from Computer Associates Technical Support at SupportCA.

  • Red Hat Linux AS 3.0

    On UNIX and Linux, the Harvest command line utilities serve as the Harvest clients. The Harvest command line utilities require one of the operating systems listed above for the Harvest server.

    Harweb on Linux requires Red Hat Linux AS 3.0

    The HSDK requires Red Hat Linux AS 3.0


    2.4 z/OS

    The Harvest 5.2.1 components for z/OS (the MVS agent and the USS agent) are posted on the Computer Associates web site, SupportCA. The posting includes the agent code, installation requirements, and a readme file (readme_harvest_mvs_uss_only.html or readme_harvest_mvs_uss_only.txt) to be used with this file, the Harvest 5.2.1 Patch 3 main readme file (readme_harvest.html or readme_harvest.txt).


    3.0 System Requirements

    This section describes the system requirements for the Harvest components supported on each operating system.


    3.1 Windows

    This section describes the system requirements for the Harvest components on Windows.

    Server

    The Harvest server on Windows requires the following hardware and software:

  • An Intel Pentium processor (Pentium III recommended).

  • 110 MB of disk space for temporary use during the installation process.

  • At least 70 MB of disk space for the Harvest product files.

  • Approximately 210 MB of disk space for the Oracle tablespaces.

  • The Harvest tablespaces require a minimum 150 MB of disk space (50 MB each for HarvestMeta, HarvestIndex, and HarvestBlob). This is the installation default. You may need to increase the size of the tablespaces based on your estimates, as follows: HarvestIndex tablespace requires approximately 600 KB and HarvestMeta tablespace requires approximately 100 KB per 1000 versions checked in. Harvest BLOB size depends directly on file size.

  • At least 128 MB of RAM. Each Harvest server process requires 15 MB of RAM.

  • Oracle 8.1.7, 9.0.1 EE, 9.2.0 EE, or 9.2.0 SE.

  • If you want to install the Harvest server with a remote database, you must do the following:

  • Ensure that the Harvest server has Oracle Server or Client Administrator installed.

  • Define an Oracle service name on the local machine, using an Oracle utility provided by the Oracle Server or Client Administrator.

    Client, Installed Locally, Not Shared

    When the Harvest client on Windows is installed locally and is not shared, it requires the following hardware and software:

  • An Intel Pentium processor (Pentium III recommended).

  • At least 60 MB of disk space for the Harvest product files.

  • At least 128 MB of RAM.

  • Network connection to a UNIX or Windows Harvest server using the TCP/IP protocol.

  • 110 MB of disk space for temporary use during the installation process.

    HSDK

    On Windows, the HSDK is installed automatically whenever you install any Harvest component, except Database and Documentation, from the Harvest product CD on a supported Windows platform. Therefore, if you meet the installation requirements for any of those components, you also meet the installation requirements for the HSDK.

    Harweb

    Harweb requires 65 MB of disk space.

    Harweb requires one of the following servlet engines. For instructions to install each of these servlet engines, see the Harvest Web Interface Install Guide in the Doc directory on the Harweb CD‑ROM.

  • Apache Tomcat 4.1.29, 4.1.30, and 5.0.25. Tomcat is available for free. For details, see the Apache web site, http://jakarta.apache.org.

  • Sun Java System Web Server 6.0 or 6.1. These editions are fully J2EE-compliant. These editions provide web server and servlet support for Harweb. For details, see the Sun web site, http://www.sun.com.

  • IBM WebSphere Application Server 5.0 or 5.1. These editions are fully J2EE-compliant. These editions also provide web server support (based on Apache 2.0) and servlet support for Harweb. For details, see the IBM web site, http://www.ibm.com.

    At publication time, Harweb does not support the following servlet engine. As soon as Harweb supports this servlet engine, installation requirements and related information will be posted on SupportCA.

  • Macromedia JRun 3.1. This servlet and JSP engine can be plugged into a commercial web server such as Apache or Sun One Web Server. For further information, see the Macromedia web site, http://macromedia.com.

    The Harweb machine requires the following to be installed locally:

  • The Harvest client

  • Java 2 SDK Standard Edition (J2SE) 1.4.2 to 1.4.2_05

    Harweb requires one of the following web browsers:

  • Microsoft Internet Explorer 6.0

  • Mozilla 1.4 to 1.7


    3.2 UNIX and Linux

    This section describes the system requirements for the Harvest components on UNIX and Linux.

    All Clients

    On UNIX and Linux, the Harvest command line utilities serve as the Harvest clients. The Harvest client (command line utility) requires 15 MB of disk space.

    All Servers

    The Harvest server requires the following hardware and software requirements on all supported UNIX and Linux operating systems. In addition to these requirements, you must meet the specific requirements for your operating system—those requirements are listed later in this section.

  • A minimum 128 MB of main memory.

  • 15 MB of virtual memory for each Harvest server process.

  • Oracle 8.1.7, 9.0.1 EE, 9.2.0 EE, or 9.2.0 SE.

  • If the Oracle database resides on a different machine than the Harvest server, SQL*Net is required.

  • Approximately 210 MB for the Oracle tablespaces.

    Note: The Harvest installation includes the following Computer Associates shared components: CA Licensing (Lic98), CAI/PT ODBC, Enterprise Communicator (PEC), and Computer Associates Cryptographic Engine (CACE). A root user account is required to install CA Licensing (Lic98). The other Computer Associates shared components can be installed to a user-specified location, which may not require a root account.

    Sun Solaris Servers

    The Harvest server on Sun Solaris requires approximately 100 MB of disk space for the Harvest product files, Lic98, CACE, PEC, and CAI/PT ODBC.

    IBM AIX Servers

    The Harvest server on IBM AIX requires approximately 200 MB of disk space for the Harvest product files, Lic98, CACE, PEC, and CAI/PT ODBC.

    HP-UX Servers

    The Harvest server on HP‑UX requires approximately 200 MB of disk space for the Harvest product files, Lic98, CACE, PEC, and CAI/PT ODBC.

    Linux for x86 Servers

    The Harvest server on Linux for x86 requires approximately 150 MB of disk space for the Harvest product files, Lic98, CACE, PEC, and CAI/PT ODBC.

    The UNIX installation program for Linux is designed for the bash shell, not the ksh shell. If your site has installed the ksh shell and linked it to /bin/sh, you must modify the installation scripts (any files which end with .sh or .SH) to specify the new location of the bash shell, such as /bin/bash.

    Harweb

    Harweb requires 65MB of disk space.

    Harweb requires one of the following servlet engines. For instructions to install Harweb and each of these servlet engines, see the Harvest Web Interface Install Guide in the Doc directory on the Harweb CD‑ROM.

  • Apache Tomcat 4.1.29, 4.1.30 to 5.0.25. Tomcat is available for free. For details, see the Apache web site, http://jakarta.apache.org.

  • Sun Java System Web Server 6.0 or 6.1. These editions are fully J2EE-compliant. These editions provide web server and servlet support for Harweb. For details, see the Sun web site, http://www.sun.com.

  • IBM WebSphere Application Server 5.0 or 5.1. These editions are fully J2EE-compliant. These editions also provide web server support (based on Apache 2.0) and servlet support for Harweb. For details, see the IBM web site, http://www.ibm.com.

    At publication time, Harweb does not support the following servlet engine. As soon as Harweb supports this servlet engine, installation requirements and related information will be posted on http://supportconnect.ca.com

  • Macromedia JRun 3.1. This servlet and JSP engine can be plugged into a commercial web server such as Apache or Sun One Web Server. For further information, see the Macromedia web site, http://macromedia.com.

    The Harweb machine requires the following to be installed locally:

  • The Harvest client (command line utility)

  • CA Cryptographic Engine (CACE)

  • Java 2 SDK Standard Edition (J2SE) 1.4.2 or 1.4.2_05

  • Enterprise Communicator (PEC)

  • Mozilla 1.4 to 1.7 web browser


    3.3 SuSE Linux s/390

    Agent

    The Harvest agent on SuSE Linux s/390 requires the following hardware and software:

  • SuSe SLES-7.0 (s390)

  • Approximately 45 MB of disk space for the Harvest product files and CA Cryptographic Engine (CACE)

    Client

    The Harvest client (command line utility) requires 30 MB of disk space.


    3.4 z/OS

    The Harvest 5.2.1 components for z/OS (the MVS agent and the USS agent) are posted on the Computer Associates web site, SupportCA. The posting includes the agent code, installation requirements, and a readme file (readme_harvest_mvs_uss_only.html or readme_harvest_mvs_uss_only.txt) to be used with this file, the Harvest 5.2.1 Patch 3 main readme file (readme_harvest.html or readme_harvest.txt).


    3.5 WebSphere Studio Integration (WSAD Integration)

    Before you install WebSphere Studio Integration (WSAD Integration), ensure that one of the following is installed:

  • IBM WebSphere Studio Application Developer 5.0 or 5.1.x Enterprise Edition

  • IBM WebSphere Studio Application Developer 5.0 or 5.1 Integration Edition

  • IBM WebSphere Studio Site Developer 5.0 or 5.1.x Enterprise Edition

  • IBM Eclipse 2.1.2

    To operate correctly, WebSphere Studio Integration requires that the Harvest client is installed locally and has access to Harweb.

    WebSphere Studio Integration 5.1 is supplied on the Harvest Release 5.2.1 installation CD. WebSphere Studio Integration 5.1 supports both IBM WebSphere Studio 5.0 and IBM WebSphere Studio 5.1. WebSphere Studio Integration 5.1 requires that one of these versions of IBM WebSphere Studio is already installed on your machine. The WebSphere Studio Integration 5.1 installation is specially customized to match the version of IBM WebSphere Studio already installed.

    Therefore, if you are using IBM WebSphere Studio 5.0 and you want to upgrade to IBM WebSphere Studio 5.1, you must perform that upgrade before you install WebSphere Studio Integration 5.1. Otherwise, you must uninstall and reinstall WebSphere Studio Integration 5.1 after you upgrade to IBM WebSphere Studio 5.1.

    After installing WebSphere Studio Integration 5.1, you must recreate your workspace.


    3.6 TestDirector Integration

    The Harvest TestDirector Integration option must be installed on the Mercury TestDirector server machine. Before installing TestDirector Integration, ensure that the following components are installed:

  • The third-party prep plug-in. This plug-in must be installed and enabled; for details, see the Mercury TestDirector Version Control Add-in Guide.

  • The TestDirector Integration third party prep plug-in and the Harvest integration require the Java JRE 1.4.0 or greater. When using TestDirector or Harvest TestDirector Integration, you must have the Java JRE active in the path prior to installation.

  • Visual C++ 6.0

  • One of the following:

  • TestDirector 8.0 with third party version control plug-in

  • TestDirector 7.6 SP3 with third party version control plug-in, build number 7.6.2.500


    3.7 Version Control Integration (VCI)

    Before installing Version Control Integration (VCI), ensure that the following components are installed:

  • IBM VisualAge 3.5.3 or 4.0

    The versions require an external version control patch from IBM.

  • One of the following certified tools for supporting the Microsoft Common Source Code Control (SCC) Interface:

  • Visual C++ 6.0 Enterprise Edition

  • Visual Basic 6.0 Enterprise Edition

    Note: In order for Visual Basic to work, you must install Visual Source Safe (VSS) because Visual Basic is not a native SCC client. Microsoft does not configure Visual Basic for SCC by default. When you install Visual Basic and choose to install Source Safe, Microsoft creates a vb.ini file in your c:winntsystem32 directory. This file sets a flag to support SCC. This configuration is specific to Visual Basic but not to Harvest. For instructions to enable SCC capabilities in Visual Basic, see the SCC help in Visual Basic.

  • Visual Studio .NET Framework 1.0

  • Visual Studio .NET 2003 Framework 1.1

  • Sybase PowerBuilder 8.0.3, 9.0, and 10.0

  • Visual Cafe 4.5.1 Enterprise Edition

  • Rational Rose 2001a.04.00

  • TogetherSoft (formerly WebGain) Visual Café Enterprise Edition 4.5.1

    Before using the VCI, complete the setup tasks in the Version Control Interface User Guide.


    4.0 Installation Considerations

    For instructions to install Harvest Release 5.2.1, see the Harvest Install Guide in the Doc directory on the Harvest installation CD.

    This section contains instructions for installing Harvest Release 5.2.1 Patch 3, running the database upgrade supplied by this patch, and changing the item access process to GRANT. This section also contains miscellaneous installation considerations for Harvest Release 5.2.1.

    Note: Harvest Release 5.2.1 Patch 3 is cumulative; that is, Patch 3 includes all fixes that were in Patch 2, plus additional fixes. You do not need to install Patch 2 before you install Patch 3.


    4.1 Installing Harvest Release 5.2.1 Patch 3 on Windows

    On Windows, Harvest Release 5.2.1 Patch 3 is supplied in two files:

  • HAR521PATCH003WIN.MSI for Harvest server and client machines

  • HARWEB521PATCH003WIN.MSI for Harweb machines

    To install Harvest Release 5.2.1 Patch 3 on Windows, follow these steps:

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

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

  • If you have already installed a previous patch, uninstall it and reboot your computer.

  • Run the HAR521PATCH003WIN.MSI file on all your Harvest server, client, and Harweb machines.

  • On the Harweb machine, you must stop your servlet engine prior to running HARWEB521PATCH003WIN.MSI.

  • Run the HARWEB521PATCH003WIN.MSI file on your Harweb machine.


    4.2 Rolling Back (Uninstalling) Harvest Release 5.2.1 Patch 3 on Windows

    To roll back (uninstall) Harvest Release 5.2.1 Patch 3 on Windows, follow these steps:

  • Log on to the operating system using the Local Administrator account.

  • Close all Harvest client applications.

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

  • Click Start on the Windows task bar and select Settings, Control Panel, Add/Remove Programs.

  • On the Add/Remove Programs dialog, select CA CA Software Change Manager Patch 3 and click Remove. This step applies to all Harvest server, client, and Harweb machines.

  • Before uninstalling Harweb, you must stop your servlet engine.

  • When rolling back this patch on a Harweb machine, select CA CA Software Change Manager Harweb Patch 3 and click Remove.


    4.3 Installing Harvest Release 5.2.1 Patch 3 on UNIX or Linux

    On UNIX and Linux, Harvest Release 5.2.1 Patch 3 is supplied in one file, <patch|fix>.tar.gz. For example, HAR521PATCH003LINUX.tar.gz. This file includes updates for all Harvest components, including client and server.

    To install Harvest Release 5.2.1 Patch 3 on UNIX or Linux, follow these steps:

  • 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 machine 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 HAR521PATCH003LINUX.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 HAR521PATCH003LINUX.tar.gz 

  • Enter the following command to un-tar the file:
     tar xvfo HAR521PATCH003LINUX.tar 

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

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

  • Change the current directory to $HARVESTHOME/PATCHES/HAR521PATCH003LINUX directory created in Step 9.

  • Enter the following command:
     ApplyPatch.sh 

  • Review the PATCH.log file in the $HARVESTHOME/PATCHES/HAR521PATCH003LINUX_BKP directory.


    4.4 Rolling Back (Uninstalling) Harvest Release 5.2.1 Patch 3 on UNIX or Linux

    To roll back (uninstall) Harvest Release 5.2.1 Patch 3 on UNIX or Linux, follow these steps:

  • Ensure that the umask is set to 022.

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

  • Close all Harvest client applications.

  • If the machine 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/HAR521PATCH003LINUX_BKP directory.

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

  • Review the PATCH.log file in the $HARVESTHOME/PATCHES/HAR521PATCH003LINUX_BKP directory.

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


    4.5 Installing Harweb Release 5.2.1 Patch 3 on UNIX or Linux

    On UNIX and Linux, Harvest Release 5.2.1 Patch 3 is supplied in one file, HAR521PATCH003UNIX.tar.gz. This file includes updates for harweb.

    To install Harweb Release 5.2.1 Patch 3 on UNIX or Linux, follow these steps:

  • Ensure that the umask is set to 022.

  • Log on to the Operating System using the UNIX Harweb account.

  • Close all Harweb Client Applications.

  • Shut down the Harweb Server components and servlet engine.

  • Change the current directory to the HarWeb home directory (<webappdir>Harweb). This directory should contain the
    directories <webappdir>HarwebHarweb,
    <webappdir>HarwebWEB-INF, and <webappdir>HarwebWebDoc.

  • Back up the following directories: <webappdir>HarwebHarweb,
    <webappdir>HarwebWEB-INF, and <webappdir>HarwebWebDoc.
    For example (within Harweb home directory):
    "tar cvf HARWEB_BKP.tar Harweb WEB-INF".

  • Copy the "patch.tar.gz" file to the HarWeb home directory(<webappdir>Harweb).

  • Delete the following files (if they exist) from the Harweb
    home directory: PATCH.log, ApplyPATCH.sh, readme_harvest.html, readme_harvest.txt.

  • Decompress the PATCH file using: "gzip -d <patch>.tar.gz".

  • Un-tar the PATCH file into the Harweb home directory
    using: "tar xvfo <patch>.tar".

  • In the <webappdir>HarwebWEB-INFlib folder, rename the following files:

  • bsf.jar → bsf.old

  • bsfengines.jar → bsfengines.old

  • xerces.jar → xerces.old

  • Execute "ApplyPATCH.sh"

  • Start the Harweb Server components.


    4.6 Rolling Back (Uninstalling) Harweb Release 5.2.1 Patch 3 on UNIX or Linux

    To roll back Harvest Release 5.2.1 Patch 3 for Harweb on UNIX or Linux, re-install the previous version of Harweb. For example, re-install the previous patch (Patch 1) or the base product installation (Release 5.2.1), whichever was installed before you installed Patch 3.

    Then in the <webappdir>HarwebWEB-INFlib folder, rename the following files:

  • bsf.old → bsf.jar

  • bsfengines.old → bsfengines.jar

  • xerces.old → xerces.jar


    4.7 Running the Database Upgrade Patch

    Harvest Release 5.2.1 Patch 3 copies but does not run database upgrade patch files to your Harvest server database machine. To upgrade your databases, run the DBPatch.sql database patch script located in the HAR521PATCH003WIN directory, using your Harvest Oracle account. You can run this database patch more than once, before or after you run Harvest Release 5.2.1 Patch 3. The DBPatch.sql database patch:

  • Is permanent

  • Is independent of Harvest Release 5.2.1 Patch 3

  • Is not intended to be rolled back

    The DBPatch.sql script is located in the HAR52PATCH003WIN directory. You can run the script after you have installed the Harvest Release 5.2.1 base product, after you have installed Patch 1, or after you have installed Patch 3.

    If you are upgrading from Patch 1 to Patch 3 and you have already run the DBPatch.sql in Patch 1, you do not have to run the DBPatch.sql again.

    Run the PR2329 script after running the DBPatch.sql. See Changing Item Access Process to GRANT for PR2329 script information.

    Run DBPatch.sql before running any external fix scripts.

    Run DBPatch.sql after completing a Harvest Release 4.1.x to 5.x conversion.

    To run DBPatch.sql, follow these steps:

  • Change the current directory to the following:

    On Unix or Linux: $HARVESTHOME/PATCHES/HAR521PATCH003WIN

    On Windows: %HARVESTHOME%PATCHESHAR521PATCH003WIN

  • Using your Harvest Oracle account, enter the following command:

    sqlplus <account>/<password> @DBPatch.sql

  • Review the DBPatch.log file in the following directory:

    On UNIX or Linux: $HARVESTHOME/PATCHES/HAR521PATCH003WIN

    On Windows: %HARVESTHOME%PATCHESHAR521PATCH003WIN


    4.8 Changing Item Access Process to GRANT

    Perform the following steps to change the item access process to use GRANT Access instead of DENY Access. These steps provide a database conversion that cannot be rolled back. After you perform these steps, you will not be able to roll back to a prior release or patch of Harvest.

  • Make a backup of your current database before you start this process. (After you run the M1 or M2 script, you cannot recover your original database).

  • Read the PR2329-readme.txt file, Tech Doc TEC324271, Grant Item Access Data Conversion and Installation Instructions, and Tech Doc TEC324326, Repository, Item Path & Item Access Model Uses GRANT Methodology Overview. See one of the following directories for the PR2329-readme.txt file:

    On Unix or Linux: $HARVESTHOME/PATCHES/HAR521PATCH003WIN

    On Windows: %HARVESTHOME%PATCHESHAR521PATCH003WIN

    Both Tech Docs are available from Computer Associates Technical Support at SupportCA.

  • Using the information and instructions in PR2329-readme.txt and the Tech Docs, run either the PR2329-M1CONVERTData.sql script (Method 1) or the PR2329-M2CONVERTData.sql script (Method 2).


    4.9 Miscellaneous

    On Windows computers, the Harvest installation may display Internal Error 2343 and abort. The most likely cause of this error is that a release of Harvest earlier than 5.2.1 is already installed. Uninstall the earlier version, using the Add/Remove Programs option from the Windows Control Panel. Then try installing Harvest Release 5.2.1 again.

    The custom installation for the Harvest client includes options to install WebSphere Studio Integration, TestDirector Integration, and WebSphere Studio Integration (WSAD Integration); however, the Harvest installation program enables only the option or options that apply to your site.

    The operating system requirements for the Harvest components on all platforms include the requirements for the applicable Computer Associates shared components such as Enterprise Communicator (PEC), CA Licensing (Lic98), Computer Associates Cryptographic Engine (CACE), and CAI/PT ODBC.

    While installing Harvest on Linux systems, if you are using Linux Red Hat 9, you must set the environment variable LD_ASSUME_KERNEL=2.4.1. If you do not set this variable, the Harvest executable files will not start. For instructions, see the Harvest Install Guide.

    On UNIX and Linux, if you are re-installing Harvest Release 5.2.1, to keep the existing Harvest Release 5.2.1 database created by the first installation, you must use installation option [2] - Upgrade Harvest. If you select option 2, you are prompted to enter the Oracle user name that owns Harvest tables. If you enter the name of the existing database user at this prompt, the installation program proceeds successfully.

    On UNIX and Linux, log on as the harvest user (not the root user) to install the Computer Associates Cryptographic Engine (CACE). For details, see the Installation section of the Known Issues in this readme file.

    Harweb

    Harweb is a standard component of Harvest Release 5.2.1. Harweb is supplied on its own CD, separate from the Harvest installation CD. There is one Harvest CD‑ROM for Windows and another for UNIX. For instructions to install Harweb, see the Harvest Web Interface Install Guide in the Doc directory on the Harweb CD‑ROM.

    Harweb uses the Harvest server's database and requires a remote Harvest agent machine.

    Harweb Windows and UNIX Agent only installations will need to apply the Harvest patch to upgrade to the current patch level.

    WebSphere Application Server

    Use these procedures to configure and deploy the Harweb under IBM WebSphere Application Server on the Microsoft Windows (2000, XP) platform. WebSphere must be properly installed and configured. Refer to the respective product documentation for further information on the installation and configuration of WebSphere Application Server.

    Prerequisites

    You need to create the harweb.war file. To do this, follow these steps:

  • Install Harweb to you local disk (follow all the normal setup instructions).

  • CD to the Harweb root dir.

  • Verify that you can run the jar command from the command line (it is installed with java).

  • Run the command line jar -cvf harweb.war * (make sure harweb.war is lowercase).

    Configuration Procedure

    Follow these configuration steps:

  • Ensure that the target WebSphere Application Server is running.

  • Start the WebSphere Application Server Administrative Console.

  • Expand the Applications entry in the Actions tree in the left frame.

  • Click Install New Application.

  • In the Preparing for the Application Installation dialog, under Path, select Local Path and enter the path name for the fully qualified path to the %temp%webapps folder on the machine where Harweb is installed and configured.

  • Under Context Root, enter /harweb. Note the presence of the prepended forward slash. Click Next.

  • Check the Generate Default Bindings check box. Click Next.

  • In the Application Security Warning dialog, click Continue.

  • In Step 1 in the Install New Application dialog, enter an appropriate name, for example, Harweb. Click Next.

  • Select appropriate site-specific options through Step 4: Summary. Click Finish when completed.

  • On the Enterprise Applications frame, select (by check box) the name you previously gave this application.

  • Select and click Start.

    Harweb is now deployed into your application server and is addressable as /harweb appended to your web application server's URL.

    WebSphere Studio Integration (WSAD Integration)

    WebSphere Studio Integration (WSAD Integration) is an optional component of Harvest client installation. For instructions to install WebSphere Studio Integration, see the Harvest Install Guide in the Doc directory on the Harvest installation CD.

    For other important installation considerations, see WebSphere Studio Integration (WSAD Integration) in System Requirements in this readme file.

    TestDirector Integration

    Mercury TestDirector Integration is an optional component on the Harvest Release 5.2.1 client custom installation. For instructions to install TestDirector Integration, see the Harvest Install Guide in the Doc directory on the Harvest installation CD.

    WARNING! If the Harvest client on the TestDirector server machine is uninstalled and reinstalled in another location after TestDirector data has been checked in to the Harvest repository, the TestDirector interface will be unable to check out the files, because of the change of location of the file htdvcElement.dtd. If the Harvest installation is moved, a copy of htdvcElement.dtd must remain in its original location.


    5.0 General Considerations

    For a list and brief description of new and changed features supplied by Harvest Release 5.2.1, see the Harvest Release Summary in the Doc directory on the Harvest installation CD.

    The Harvest Release 5.x HSDK replaces the Harvest SIK supplied with Harvest Release 4.x and earlier versions. The Harvest SIK was a C language interface to a subset of the Harvest capabilities. The HSDK is a C++ class set for the same functionality. SIK functionality can be reprogrammed using the HSDK but is not directly compatible with the HSDK.


    6.0 List of Fixes

    Harvest Release 5.2.1 Patch 3 includes all Release 5.2.1 Patch 2 and Release 5.1.1 fixes. These fixes were originally created for Harvest Release 5.1.1 patches 16‑18, WebSphere Studio Integration (WSAD Integration) Release 2.0 patches 5‑7, and Harweb Release 3.1 patches 10‑12. A list of fixes is on our web site, SupportCA.


    6.1 Harvest Release 5.2.1 Patch 2 Fixes

    PR 0766 - HCO-CHECK OUT FOR SYNCHRONIZE CHECKS OUT RESERVED VERSION

    PR 1130 - CREATION AND MODIFICATION TIME IS THE SAME IN DATA VIEWS

    PR 1382 - ERROR MESSAGE IS RETURNED WHEN USER DOESN'T ENTER FORM NAME

    PR 1448 - WRONG TIME IN PACKAGE HISTORY REPORT

    PR 1478 – VCI (ROSE) - CANNOT INCLUDE FILES IN DIRECTORIES HIGHER THAN HP~

    PR 1663 - RECURSIVE SEARCH VIA SHELL-EXTENSION SHOWS INCORRECT VIEWPATH

    PR 1706 - VCI - VB GPF WHEN PERFORMING CREATE PRJ FROM HARWITH PROJ CONTAINING COMMON FIL

    PR 1789 - HARWEB INSTALL CHANGING DEFAULT TIMEZONE OF JVM

    PR 1875 - CAN'T RESTORE PROJECT WHEN THERE ARE RESERVED TAG VERSION

    PR 1993 - FILE TIMESTAMP NOT IN GUI

    PR 2007 - CANCEL CLOSES DATAVIEW

    PR 2143 - CALL PROCESS OUT OF PROJECT BY COMPARE VIEW

    PR 2349 - HCO FAILS WHEN ITEM WITH FULL PATH

    PR 2393 - HSQL CONVERTS DATE

    PR 2401 - HSDK CAVERSIONCHOOSER API RETURNS NO FILESIZE

    PR 2405 - VERSION WHEN USED AS PRELINK UDP DOESN'T GET VIEWPATH INFO

    PR 2434 - HARVEST CLIENT DOES NOT DISPLAY SIZE OF AN ITEM

    PR 2466 - NOTIFY PROCESS - WRONG NAME

    PR 2564 - HEXECP FAILS ON WINDOWS AGENT WHEN RUNNING MORE THAN 32 TIMES

    PR 2593 - HARVEST REPORTS - DATE FORMAT INCORRECT

    PR 2621 - CHECKIN FAILS ON FILES WITH SAME FILENAME BUT DIFFERENT CASE

    PR 2633 - STRANGE OUTPUT FOR THE UDP SCRIPT WHEN RUNNING IN HARVEST

    PR 2793 - NOT SHOW CHECKOUT MARKS AFTER ADD AND RESERVE IN WSAD

    PR 2796 - SYNC PROBLEM AFTER COPY/PASTE A ITEM

    PR 2809 - FIND VER LIMIT VIEW TO STATE WHEN VIEW OPT IS VER FILTER ALL

    PR 2810 - FIND VER/DELETE VER SQL ERROR ORA-01795 OVER 1000 ITEMS SEL

    PR 2857 - HARVEST GPF WHEN DRAG PACKAGE WITH NO PROMOTE TO STATE

    PR 2894 - VCI-NEW FILES NOT RECOGNIZED ON USER 2 MACHINE

    PR 2977 - VCI - PERFORMANCE PROBLEMS WHEN ADDING PROJECTS ON UNIX

    PR 2979 - HARWEB VISUAL DIFFERENCE SHOWS INCORRECT FILE

    PR 2981 - HARVEST ADMIN MAY FAIL WHEN REORDERING STATES

    PR 2982 - CANCEL BUTTON IN SELECT HARWEB CONTEXT BRINGS HARWEB

    PR 2984 - HEXECP -ASYN PRODUCES AN ERROR AFTER SECOND CALL.

    PR 2985 - OSF AGENT WILL ERRANTLY PRODUCE A LOCKED DIRECTORY MESSAGE

    PR 2986 - CLICK SYMBOLIC LINE FOLDER FOR CHECKIN IN HARWEB FAILS

    PR 2997 - LATEST_IN_PACKAGE/ALL_IN_PACKAGE MISSING HSDK

    PR 3016 - VCI-VDIFF DOES NOT WORK WHEN CO HAS PRELINK UDP THAT FAILS

    PR 3028 - Checkin Non-reserved item takes a long time

    PR 3033 - Harvest ADDS 0x0D [CR] character in compressed Text Repository

    PR 3045 - PASSWORD CORRUPTED IN UDP

    PR 3051 - HUSRMGR RETURNS AN ERROR WHEN NO USER GROUP SPECIFIED

    PR 3053 - HIMPENV HANGS WITH OPTION -IUG

    PR 3054 - RUNTIME ERROR WHEN SET CONTEXT TO PROJECT WITH LONG NOTES

    PR 3056 - REFRESHING THE VERSIONS LIST WILL GET UNKNOWN ERROR

    PR 3058 - CHECK IN FOLDER PROBLEM WHEN FOLDER NAME HAS SPACE

    PR 3068 - CANCEL TAKES LONGER TIME THAN OK IN NOTIFY PROPERTIES WINDOW

    PR 3079 - VCI - Doc needed for common directory

    PR 3081 - Add empty projects to workspace

    PR 3086 - TIMESTAMP DISPLAY INCORRECT WHEN TIMEZONE IS GMT +/- #.5HR

    PR 3089 - STATES ARE BEING PRESENTED ALPHABETICALLY ORDERED

    PR 3090 - HCO CORE DUMP WITH LARGE NUMBER OF FILES ON UNIX

    PR 3092 - FILE AGENT ERROR WITH HCO

    PR 3093 - CLIENT UDP CAUSES WORKBENCH LOSING FOCUS

    PR 3096 - LIST VERSION WITH ACTUAL CHANGES SHOWS NOTHING IN OUTPUT

    PR 3101 - FILE EXTENSION FOR COMPRESS NOT RECOGNISED CORRECTLY

    PR 3106 - CHECKIN WITH DELETE OPTION GET ERROR CANNOT OPEN SIG

    PR 3124 - HARVEST LOGS ERROR WHEN CHECK OUT FROM EMPTY DIRECTORY

    PR 3171 - CAVERSIONCHOOSER Update to HSDK Guide

    PR 3176 – XERCES/XLAN UPGRADE

    PR 3182 - PROMOTE TAKING 100% OF CPU

    PR 3191 - HCI - DCP & -DVP OPTIONS MISSING

    PR 3192 - CREATE WEB XML FOR TOMCAT 5.0

    PR 3206 - MODIFY FORM TABLE IN USER CONTACT.HFD AND MODIFICATION REQUEST.HFD FILES

    PR 3209 - TOMCAT DIRECTORY SPACE INSTALLATION

    PR 3251 – RESOLVE THE HOSTNAME TO AN IP ADDRESS TO BE ABLE TO CONNECT TO THE AGENT

    PR 3254 - PACKAGE ASSOCIATED FORMS NOT DELETED

    PR 3263 - FILE AGENT ALLOWS CHECKIN OF FILE W/O PERMISSIONS

    PR 3286 - COMPARE VIEW CAUSES PROBLEM


    6.2 Harvest Release 5.2.1 Patch 3 Fixes

    PR 3443 - NON-ADMIN USER CAN'T CHECK OUT FILES WITH HARVEST 521 P2

    PR 3444 - DIFFERENT VERSION OF ADVANTAGE.EXE INSTALLED AFTER P2

    PR 3456 - COMPARE FILE/VERSION RUNTIME ERROR

    PR 3473 - WEB.XML NOT INSTALLED WITH PATCH 2


    7.0 Known Issues

    This section lists the most prominent known issues for Harvest Release 5.2.1 at publication time. For other known issues, see Computer Associates Technical Support at SupportCA.


    7.1 Access Control

    PR2910: A User Group that does not have View access to an item path can modify the item path through command line utility check in process (hci).

    PR2329: Harvest Release 5.2.1 Patch 1 includes files and steps for changing the item access process to use GRANT Access instead of the DENY Access. If you perform these steps, you will not be able to roll back to a prior release or patch of Harvest, because these steps perform a database conversion that cannot be rolled back. For more information, see Changing Item Access Process to GRANT under Installation Considerations in this readme file.


    7.2 Agent Connection Problems

    PR3118: When you attempt to connect to a remote agent by using the Connect to New Agent option of the Remote Agent Neighborhood on the Files tab of the Harvest Workbench GUI, you receive a login timeout error if both of the following conditions exist:

  • The machine name of your Harvest broker includes a dash (-)

  • The remote agent is already connected to that broker

    As a workaround, try either renaming the current broker (if feasible) or using a different broker.

    PR3117: When you connect to a remote agent by using the Connect to New Agent option of the Remote Agent Neighborhood on the Files tab of the Harvest Administrator or Workbench GUI, the GUI caches the agent connection information.

    If the remote agent is shut down and restarted, you must disconnect and reconnect the agent in the Remote Agent Neighborhood to reestablish the cached agent connection information. If you do not do so, the GUI cannot perform remote agent file handling, even though the remote agent appears valid on the Files tab.


    7.3 Agent Modes

    PR2911: A user cannot start multiple single-user agents on the same machine connecting to different Harvest brokers (rtservers) on a z/OS machine with SuSE Linux 7.0 installed.


    7.4 Agent Shutdown

    PR3109: On HP-UX, Solaris, and z/OS, when the RT server or Harvest broker is shut down, the Harvest agent also shuts down. This problem may also affect other platforms. If you experience this problem, first restart the RT server and the broker and then restart the agent.


    7.5 Check In and Check Out

    PR2912: Generally, two Harvest users can share the same project files; that is, the users can both have the same files checked out simultaneously, and their changes can be merged when both files are checked in again. This ability to share files does not apply to Sybase PowerBuilder project files.

    PR2913: On Windows, if you check in or check out files using HarWind (the Harvest Windows Extension) after you install the Harvest client, you may receive error messages similar to the following, even if the files are actually checked in or checked out properly:
     E3080003: Requested Message Key Not Found: : HSRV_I_CHECKIN  E3080003: Requested Message Key Not Found: : HAPI_I_EXECUTE_SUCCESS  E3080003: Requested Message Key Not Found: : HSRV_I_CHECKOUT E3080003: Requested Message Key Not Found: : HSRV_I_CHECKOUT 

    To fix this problem on Windows 2000, restart the computer.

    To fix this problem on Windows XP, close and restart all Windows Explorer sessions.

    PR2988: If you are using Harvest with any supported IDE, such as PowerBuilder, and you check out a project, you will not be able to see files added to that project by other users until the next time you check in the project. Therefore, we recommend that you check out projects for brief time periods only and that you check in projects as frequently as possible.


    7.6 Command Line

    PR2914: The project restore command line utility named hrt requires a remote file agent connection on the machine where the project was archived. For example, to restore a project to Harvest from machine A, a remote file agent must be running on machine A. Use the following syntax for hrt:
     hrt -b <broker> -f <archive file> -m <machine> -musr <user> -mpw <password>     -user <harvest user> -pw <harvest pw> 


    7.7 Form Management

    PR2915: To use the database combo control in Harweb, the SQL query must include the object ID. For example, the following is a simple query on the Harvest username:
     select usrobjid, username from haruser 

    The object ID does not appear in the combo control list.


    7.8 Graphical User Interface

    PR2916: The function for copying multiple Lifecycle processes in the Harvest Administrator from one state to another does not work. You must copy each process individually.

    PR2917: In the Administrator interface, the Add and Delete buttons are disabled on the Access tab of the linked process properties dialogs, because access to a linked process is controlled by its parent process. A user group granted access to execute a process has implicit access to execute the linked processes.

    PR2918: The remove item process is slow. For example, removing approximately 25 items requires approximately one minute. The efficiency of the removal decreases as the number of items to be removed increases. Also, after each item is deleted, certain pre-link and post-link UDPs are executed automatically. Consequently, pre-link and post-link UDPs are practically unusable for the remove item process.

    PR2919: The promote process may be very slow if you promote a large number of packages (for example, 200) with Verify Package Dependencies and Enable Package Merge selected.

    PR2920: In the Workbench Check Out dialog, the following problems may occur:

  • Making a selection from the file browser changes the setting for the Context View Path, even if Use Context View Path is checked.

  • Clearing the Use Client View Path check box also changes the Context View Path, even if Use Context View Path is checked.

  • The Client View Path may be changed when you browse files if Use Context View Path is not checked or if Use Client View Path is checked.


    7.9 Harweb

    These issues apply to the General Web Client.

    PR2921: The compare view process does not allow a user to select an alternate view name (other than the default Working View) unless the Public user group is granted Use access to the project. The View Chooser says No View. To work around this problem, add the Public user group to the Use access method for the Harvest project in the context.

    PR2922: The create package process does not format the package name correctly if the package name includes one or more double quotation marks ("). If you specify a package name that includes a double quotation mark, Harvest assigns the default package name instead of the name you specified.

    PR2923: The create package process does not display the associated form if the package name contains one or more single quotation marks ('). If you specify a package name that includes a single quotation mark, Harvest issues a Confirmation Message and closes the form. To display the form, open the Package Properties dialog and use the Forms tab to locate the form.

    PR2924: In Harweb, you cannot use a hyphen (-) as the first character of a package name. If you attempt to name a new package or rename an existing package with a hyphen (-) as the first character, the attempt fails.

    PR2925: Harweb users cannot check out all files in the repository by specifying only the root path as the path name for the files to be checked out. Thus, if the default view path—the root path ()—is set as the View Path Anchor, Harweb users cannot check out the versions displayed when they execute Find Version.

    PR2926: If you are using Harweb hosted in IBM WebSphere Studio and you require Tomcat, you must use Tomcat 4.0.6. For details, see System Requirements earlier in this readme file.


    7.10 Installation

    PR2927: The Harvest server does not support fully qualified host names, for example name.domain.com or name1.name2.domain.com. If the host name is fully qualified, the Harvest server fails to start. To work around this problem, follow these steps:

  • Define a host name alias as name or name1 for the fully qualified host name.

  • Define an environment variable, $RT_FORCE_NODE_NAME on UNIX or a system variable RT_FORCE_NODE_NAME on Windows and set it to the alias defined in step 1 above.

  • Restart the Harvest broker and RTserver if they are already running.

    PR2928: The Computer Associates shared components required by Harvest are CA Licensing (Lic98), CA Cryptographic Engine (CACE), CAI/PT ODBC, and Enterprise Communicator (PEC). Generally, on Windows, Computer Associates products install each of these components in the Program FilesCA directory.

    PR2929: On the s/390 machine running SuSE Linux 7.0, the command line utilities-only installation does not prompt you to enter the location of RTHOME; however, the installation completes successfully. The command line utilities-only installation includes the PEC library files.

    PR2930: On UNIX and Linux, if you are re-installing Harvest Release 5.2.1, to keep the existing Harvest Release 5.2.1 database created by the first installation, you must use installation option [2] - Upgrade Harvest. For details, see Installation Considerations.

    PR2989: When installing the Harvest server on Windows, use the Oracle SYSTEM account (or another account with the required DBA privileges). If you use the Oracle SYS account, the installation program may "hang" (stop but not close) without displaying error messages. If you experience this problem, use the Windows Task Manager to close the installation program. Then run the installation program again, using the Oracle SYSTEM account.

    PR2990: In the chapter "Installing on UNIX and Linux," the Harvest Install Guide incorrectly states that you must log on to UNIX or Linux as the root user to install the Computer Associates Cryptographic Engine (CACE). You can install CACE on UNIX or Linux under a non-root account. The Harvest Release 5.2.1 CACE installation accepts an installation path directory argument.

    PR2991: On the Harvest Release 5.2.1 Installation CD, the cmdonly folder contains a subfolder for Enterprise Communicator (PEC) 4.5 on s/390. This subfolder is not necessary, because the Harvest command-line-utilities-only installation on z/OS includes the PEC files with the Harvest library files. Therefore, you can ignore this subfolder.


    7.11 Illegal Characters

    PR2931: On Windows, a load repository command fails with the following error message if the repository name includes a forward slash (/) or backward slash ():
     Harvest Output: "E03020151: Error: Invalid View Path:   " 

    Therefore, ensure that the Harvest repository name includes no forward or backward slashes.

    PR2932: If you rename a checked-in item to include illegal Harvest characters and then attempt to check out the new version, the check out attempt fails with the following error message:
     Harvest Output: "E03020028: File Agent error for item : Permission denied." 

    On Windows, the following characters are illegal and therefore cannot be used in Harvest file names:

  • quotation mark (")

  • forward slash (/), backward slash (), or vertical separator (|)

  • colon (:)

  • asterisk (*)

  • question mark (?)

  • carets (< >)

    On UNIX and Linux, the forward slash (/) is illegal and may not be used in Harvest file names.

    PR2933: If you are using international character codes and a 5c character code is the last character of the path name of the Harvest repository, then any attempt to load the repository fails. Similarly, a check in or check out attempt fails if a 5c code character is the last character of the path name of the directory specified in the check in or check out.


    7.12 Linux

    PR2934: If you are installing Harvest on Linux Red Hat 9, you must set the environment variable LD_ASSUME_KERNEL=2.4.1 after the installation. For details, see Installation Considerations earlier in this readme file.


    7.13 Password Policy

    PR2935: When AllowUsernameAsPassword = false, a password can be the user's name if the case of one or more letters is different. For example, user rabbit can create password RABBIT, Rabbit, raBBit, and so on. Validation fails only on password rabbit.

    PR2936: A user with a # character at the beginning of the user name (for example, #uno) cannot receive a user override using hppolset because # denotes a comment in the password policy configuration file.


    7.14 Security Concerns

    PR2937: Installing the Harvest components requires only system user access (the system user named harvest). However, installing the required Computer Associates shared components for the first time requires root user access. The Computer Associates shared components required by Harvest are CA Licensing (Lic98), CA Cryptographic Engine (CACE), CAI/PT ODBC, and Enterprise Communicator (PEC).


    7.15 Version Control Interface (VCI)

    PR2938: When you are using Harvest with the Version Control Interface (VCI) on Windows 2003 or Windows .NET, setting the Check out Automatically option of the Tools, Options dialog does not check out files automatically. Use the following steps as a work around:

  • Open the Options dialog.

  • Select the Check out automatically option.

  • Ensure that this option is not selected: allow checked in items to be edited.

  • In your Harvest project, remove all check out processes except check out for update.

  • Open the Checkout Properties dialog and ensure that Update is the only mode enabled.

    After you have completed these steps, if you edit a checked in file, the file is checked out automatically without invoking any dialog.

    PR2939: When checking out files using Version Control Interface with Visual Studio 6.x or Visual Studio .NET, you may use the Synchronize or Browse checkout option from the Advanced Checkout dialog. Synchronize synchronizes the project in Harvest with the versions on the local file system. Browse replaces the files on the local file system with the latest versions from Harvest. Both operations will complete successfully in Harvest. Afterwards, the files remain checked in and read-only. However, both operations appear to fail because Visual Studio displays an error message. This error message is displayed because Visual Studio does not support these features.


    7.16 WebSphere Studio Integration (WSAD Integration)

    PR2998: If you open a resource in the Navigator by right-clicking and selecting Open in New Window, then both windows are closed when close the new window.

    PR2999: WebSphere Studio Integration does not support refactoring of folders.

    PR3000: The user interface sometimes becomes unstable when you are using package lists, version lists, or item lists that contain more than 5000 list items. To avoid this problem, close the Harvest list view when you are working with extremely large projects or lists.

    PR2940: While working in the Workspace, suppose you close a project and disconnect from the Harvest repository. If you then open the same project and attempt to synchronize, you may receive a message similar to the following:
     An unexpected Error has occurred 

    This message means that the connection to the Harvest repository is not available, because you disconnected from it earlier.

    PR2941: If you check out several files, switch to a different context package, and then attempt to check in those files, the check in attempt fails. An ambiguous error message is displayed, and the files are marked as checked out on the local workspace.

    PR2942: If you are using WebSphere Application Server 4.0.x or 5.x as your Harweb web server, you are logged out the first time you start Harweb from WebSphere Studio, after you press any key. This logout happens only once after your initial logon. Afterwards, you can start Harweb from WebSphere Studio without being logged out.

    PR2943: Before you can delete a folder in the WSAD Integration Navigator view, you must do the following:

  • Use the Harvest Administrator interface to delete the folder and all its items.

  • Synchronize with Harvest in WSAD Integration.

    PR2944: While working in project, if you rename an item and then attempt to rename it back to its old name, you receive an error message similar to the following:
     Cannot rename item; new name already exists. 

    The functionality to rename an item and then rename it back to its old name is not supported by the Harvest architecture or WSAD Integration.

    PR2945: If WebSphere Studio users are forced to change their passwords when logging in to WebSphere Studio and then try to open their projects in Harvest repositories, they are denied access and receive an "incorrect login" message. To open their Harvest projects, these users must log out of WebSphere Studio and log back in, using their new passwords.

    PR2946: Suppose that two users are working on the same package, and one user runs an interactive merge process while the second user wants to check out files for that package. The first user running the interactive merge process is locking the package so that the second user cannot check out the files. The second user receives a message displaying that the files are locked because an interactive merge process is in progress. The message displays the machine name (but not the user name) that has the files checked out.

    PR2947: If a process is changed in the Harvest Admin GUI while WebSphere Studio Integration is open, WebSphere Studio Integration does not display the change until it (WebSphere Studio Integration) is stopped and restarted.

    PR2948: If the Client Path entered in the Set Harvest Context dialog is read-only and you attempt to use the Add to Workspace function, the attempt fails and an error message is displayed. This error message does not specify that the path is read-only.

    PR2949: If you are using Harweb hosted in IBM WebSphere Studio and you require Tomcat, you must use Tomcat 4.0.6. For details, see System Requirements earlier in this readme file.

    PR2950: When you replace the latest version of a file with a previous version, and attempt to edit this previous version, the file is checked out as the latest version.

    PR2951: This issue applies if you perform the following steps while using WSAD 5.1.1 and Eclipse 2.1.2 with Harvest Release 5.2.1:

  • Create a project, add files, share the project with Harvest, and then rename one or more of the files.

  • In Navigator view, select Replace With, Version In Harvest.

    In the Version Compare window, select version 0 (N), right-click, and select Checkout (Check out for concurrent update must be available).

  • From WSAD Integration, attempt to perform any of the following operations on a renamed file, from the Team menu: Undo Checkout, Check In and Keep, or Check In and Release. Each attempt results in the following errors:
     E0202011b: Error: Item has been previously renamed within the project.         Check in failed for file: D:Workspace_WSSDprojoffline.txt  E03060019: ERROR: Process Execute failed. Process Name: Check In Items. 

    PR2952: When logging in to Harvest, you can modify the Client Path field on the Set Harvest Context dialog; however, Harvest always ignores changes to that field and uses the default path name.

    PR2953: If you share a project, un-share it, immediately share it again, and then attempt to use the Move and Delete functions for the files in that project, the attempt fails, and Harvest displays an error message similar to the following:
     Problems occurred moving the selected resources:  Resource is out of sync with the file system... 

    To fix this problem, manually refresh the files by double-clicking them.


    7.17 Direct Connect Considerations

    The implementation of direct connection from Client to Server, Client to Remote Agent, and Remote Agent to Server introduces the following requirements:

  • Client to Server (for example: checkout to local file system): Client host must be able to resolve the Server's hostname to an IP address.

  • Client to Remote Agent (for example: login to Remote Agent): Client host must be able to resolve the Remote Agent's hostname to an IP address.

  • Remote Agent to Server (for example: checkout to Remote Agent): Remote Agent host must be able to resolve the Server's hostname to an IP address.

    Note: Hostname refers to a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-). No distinction is made between upper and lower case. The first character must be an alpha character. The last character must not be a minus sign.


    8.0 Language Certifications

    After English GA, the English versions of the Harvest server, client, agent, and Harweb have been certified to run on machines designed to use the following languages: French, German, Spanish, Italian, Portuguese (Brazil), Japanese, Korean, Traditional Chinese, and Simplified Chinese. This certification means that these English versions can run on the non-English operating systems on those machines. It is not intended to mean that these versions are localized for those markets and languages.


    9.0 Documentation

    Each PDF guide in a documentation set has a unique Document ID (DID) that appears on the title page of the guide. The DID uses the first six characters to identify the guide, a hyphen, then two characters at the end to identify the edition and language in which it is written. For example, xxxxxx-1E identifies the first edition of the English version of the <Product Name> <Guide_Name>. When the second edition of this guide is published, the DID is incremented to xxxxxx-2E. The DID is used without the hyphen for the .PDF file on the product media and on SupportConnect as shown in File Name column of the following table.

    The DIDs and file names for the Harvest guides are:


    10.0 Contacting Technical Support

    If you need technical assistance with this product, access the Computer Associates web site, SupportCA, where you can quickly locate answers to many questions. Technical support is available 24 hours a day, 7 days a week.


    11.0 Downloads

    CA Software Change Manager 5.2.1 patches are available as two separate downloads:

    Apply the HARVEST patch to all Harvest Installations.

    Apply the HARVEST and HARWEB patch to the Harweb Installation.

    For the MVS and USS Agent downloads, additional details are located on the download page for each agent.

    Guide Name DID File Name
    Administrator Guide E00094-3E E000943E.PDF
    COM SDK Reference Guide E00104-2E E001042E.PDF
    Getting Started E00095-2E E000952E.PDF
    Install Guide E00096-2E E000962E.PDF
    Integration Tools User Guide E00102-1E E001021E.PDF
    Reference Guide E00097-3E E000973E.PDF
    Release Summary E00110-1E E001101E.PDF
    Sample Reports User Guide E00105-2E E001052E.PDF
    SDK Reference Guide E00109-3E E001093E.PDF
    Tutorial Guide E00098-2E E000982E.PDF
    Harvest User Guide E00099-2E E000992E.PDF
    Version Control Interface User Guide E00108-3E E001083E.PDF
    Web Interface Install Guide E00107-2E E001072E.PDF
    Readme E00134-1E E001341E.html
    Product Operating System - File Size
    README (Harvest & Harweb) HTML - 75.0 KB TEXT - 70.1 KB            
    HARVEST Windows - 55.1 MB Solaris - 8.5 MB AIX - 14.1 MB HP-UX - 15.0 MB RedHat Linux - 3.4 MB SuSE Linux - 4.0 MB MVS USS
    HARWEB Windows - 42.0 MB Unix - 41.0 MB            
  • 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