Support Content Notification - Support Portal

Welcome to AllFusion Harvest Change Manager r7.1 (AllFusion Harvest). This readme contains installation considerations, operating system support, known issues, and instructions for contacting CA Customer Support.

This readme covers all standard and optional components for AllFusion Harvest r7.1:

The AllFusion Harvest server, client, agent, and command line utility
The AllFusion Harvest SDK components: the HSDK, the Java SDK (JHSDK), and the Component Object Model SDK (COM SDK)
AllFusion Harvest Change Manager Sample Reports
AllFusion Harvest Change Manager TestDirector Integration (TestDirector Integration)
AllFusion Harvest Change Manager Version Control Interface (VCI)
AllFusion Harvest Change Manager Web Interface (Harweb)

1.1 Plug-in for Eclipse

To use AllFusion Harvest r7.1 with AllFusion Harvest Change Manager Plug-in for Eclipse (AllFusion Harvest Plug-in for Eclipse), you must use the version of AllFusion Harvest Plug-in for Eclipse that is compatible with AllFusion Harvest r7.1. For further information, see your CA account representative.

For information about generally available (GA) versions of AllFusion Harvest Plug-in for Eclipse that work with GA versions of Harvest, see the AllFusion Harvest Plug-in for Eclipse documentation, including the AllFusion Harvest Plug-in for Eclipse Readme, at http://supportconnectw.ca.com/public/harvesteclipse.

2.0 Operating System Support

This section lists the operating systems supported by AllFusion Harvest r7.1 components at publication time. CA supports each operating system for the duration of its life cycle (as determined by its manufacturer) or until CA announces that we are no longer supporting it. For the latest information about supported operating systems, including any updates that may have occurred after publication, see the AllFusion Harvest Compatibility Matrix provided by Customer Support at https://support.ca.com.

2.1 Windows

This section lists the Windows operating systems supported by AllFusion Harvest r7.1 components.

Multiple Components

The AllFusion Harvest server, client, agent, and Harweb require one of the following operating systems:

Windows 2000 Server

Windows 2000 Advanced Server

Windows 2000 Professional

Windows Server 2003 Standard

Windows Server 2003 Enterprise

Windows XP Professional

Harweb

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

Microsoft Internet Explorer 6.0
Mozilla 1.4 to 1.7
Mozilla Firefox 1.5

Sample Reports

The database server running the AllFusion Harvest Sample Reports component requires a Windows operating system that supports CA Software Change Manager Server r7.1. The database server is the computer that stores the Harvest database.

A computer running Sample Reports locally requires one of the following operating systems:

Windows 2000
Windows XP

A server hosting Sample Reports on a network requires one of the following operating systems:

Windows 2000 Server
Windows 2000 Advanced Server
Windows 2000 Professional
Windows 2003 Server
Windows 2003 Advanced Server

A client accessing the host server for Sample Reports requires a Windows operating system that supports the following:

CleverPath Forest & Trees Runtime Option 7.0
Microsoft Internet Explorer 6.0

LDAP Authentication

LDAP authentication for AllFusion Harvest multi-user agents is supported on the following Windows platforms:

Windows 2000 Server
Windows 2000 Advanced Server
Windows 2000 Professional
Windows Server 2003 Standard
Windows Server 2003 Enterprise
Windows XP Professional

Note: For information about LDAP authentication for AllFusion Harvest multi-user agents, see the chapter "Configuring Harvest Communication" in the CA Software Change Manager Administrator Guide.

2.2 UNIX

Important! If you are using Sun Solaris 8, your operating system must have the required patches installed to support the CA Cryptographic Engine (CACE). For details, see Installation Considerations in this readme.

This section lists the UNIX operating systems supported by AllFusion Harvest r7.1 components.

Multiple Components

On UNIX, the AllFusion Harvest server, Harweb, client (command line utilities), and agent require one of the following operating systems:

Sun Solaris 8, 9, or 10
HP-UX PA-RISC 11.00, 11i
HP-UX Itanium 11.23
IBM AIX 5.1, 5.2, or 5.3

Additional requirements and information follow, as needed, for each component.

Command Line Utilities (including HSDK and JHSDK)

The AllFusion Harvest command line utilities on UNIX serve as the AllFusion Harvest clients.

The HSDK and JHSDK are installed automatically when you install the command line utilities.

Note: If you are using Solaris 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, replace the following statement:
```
#if defined(__hpux)
```
with this statement:
```
#if defined(__hpux) || ( __SUNPRO_CC >= 0x500 )  
```

The HSDK on AIX requires AIX 5.1, 5.2, or 5.3 and the IBM XL C/C++ compiler for 7.0.

The HSDK on AIX or HP-UX requires stlport 4.6.2.

The HSDK on Solaris requires stlport 4.5, which is supplied with the Sun compiler SunOne Studio 8.

You can download these stlport versions from the stlport web site, www.stlport.org.

LDAP Authentication

Multi-user agent LDAP authentication is supported on the following UNIX platforms. Your UNIX operating system must support random number generators for TLS certificates, as noted in the following list:

IBM AIX 5.1, 5.2, 5.3

OpenSSH on these versions of AIX is compiled using the entropy gathering mechanism (random numbers) provided with the OpenSSH source code (ssh-rand-helper).

The AIX 5.1, 5.2, or 5.3 base security provides new pseudo random number generator devices, /dev/random and /dev/urandomM.

Hewlett-Packard HP-UX
The /dev/random and /dev/urandom devices are not available on certain release of HP-UX 11.x. They are available as part of the "rng" software kit and can be downloaded from http://hp.com.
On Sun Solaris 8, Patch 112438-03 or higher is required for random number generation.
Note: For information about LDAP authentication for Harvest multi-user agents, see the chapter "Configuring Harvest Communication" in the CA Software Change Manager Administrator Guide.

2.3 Linux

This section lists the Linux operating systems supported by AllFusion Harvest r7.1 components.
Multiple Components
On Linux, the AllFusion Harvest server, Harweb, client (command line utilities), and agent require one of the following operating systems:
Additional requirements and information follow, as needed.
Command Line Utilities (including HSDK and JHSDK)
On Linux, the AllFusion Harvest command line utilities serve as the AllFusion Harvest clients.
The HSDK and JHSDK are installed automatically when you install the command line utilities.
Important! If you are using Linux, your operating system must have the required files and rpm packages installed. For details, see Installation Considerations in this readme.
LDAP Authentication
Multi-user agent LDAP authentication is supported on the following Linux platforms. Your Linux operating system must support random number generators for TLS certificates, as noted in the following list:
On Red Hat Enterprise Linux, the /dev/random and the /dev/urandom devices are installed by the base operating system as part of the dev rpm (for example, dev-3.3.8-1 on Red Hat Enterprise Linux Advanced Server 3.0).
Ingres
If you select Ingres as your DBMS for Harvest server, you need to install the Harvest server on Novell SUSE LINUX Enterprise Server 8 or 9.

2.4 z/OS

The AllFusion Harvest z/OS agent enables an AllFusion Harvest client to access a remote USS file system or MVS data sets.
The ISPF client provides check in and check out to MVS partitioned datasets via ISPF panels.
The z/OS agent and ISPF client require z/OS 1.4, 1.5, 1.6, or 1.7.
On z/OS, Harvest supports partitioned data sets and HFS files.

2.5 Novell SUSE LINUX Enterprise Server for s/390

The AllFusion Harvest client (command line utility) and agent on Novell SUSE LINUX Enterprise Server 8 or 9 for s/390 require Novell SUSE LINUX Enterprise Server 8 or 9 for s/390.

3.0 System Requirements

This section describes the system requirements for the AllFusion Harvest components supported on each operating system.
At publication time, AllFusion Harvest r7.1 supports the third-party software, including DBMS software, application servers, and web browsers, listed in this section. These supported third-party software products are listed according to operating system. For the latest information about supported third-party software, including any updates that may have occurred after publication, see the AllFusion Harvest Compatibility Matrix provided by Customer Support on https://support.ca.com.

3.1 Windows

This section describes the system requirements for the AllFusion Harvest components on Windows.
Server
The AllFusion Harvest server on Windows requires the following hardware and software:
AllFusion Harvest Server with a Local Ingres Database (New Installation)
For a first-time installation, the AllFusion Harvest server computer with a local Ingres database requires the following:
AllFusion Harvest Server with a Local Ingres Database (Upgrade)
If you are upgrading an existing Harvest server with a local Ingres database, the same requirements as a new installation apply, except that you may require more disk space. To determine the amount of disk space you need, do the following:
HP-UX PA-RISC 11.00, 11i
HP-UX Itanium 11.23
Sun Solaris 8, 9, 10
Red Hat Enterprise Linux Advanced Server 3.0 and 4.0 and Red Hat Enterprise Linux Enterprise Server 3.0 and 4.0
Novell SUSE LINUX Enterprise Server 8 or 9 for x86 with an ext3 file system
Red Hat Enterprise Linux Advanced Server 3.0 and 4.0 and Red Hat Enterprise Linux Enterprise Server 3.0 and 4.0
Novell SUSE LINUX Enterprise Server 8 or 9
On Novell SUSE LINUX Enterprise Server, the /dev/random and the /dev/urandom devices are installed by the base operating system as part of the dev rpm (for example, devs-2002.10.4-9 on SUSE LINUX Enterprise Server 8).
An Intel Pentium processor (Pentium 4 recommended).
A minimum 512 MB of RAM for running AllFusion Harvest.
A minimum 1 GB of RAM for running both AllFusion Harvest and Ingres.
110 MB of disk space for temporary use during the installation process.
At least 70 MB of disk space for the AllFusion Harvest product files.
A local or remote database running a supported version of Oracle, Ingres, or Microsoft SQL Server. Details about each DBMS's requirements are provided in this section.
An Intel Pentium processor (Pentium 4 minimum).
Disk Space: 7 GB recommended.
Memory: 1 GB RAM, minimum. Each Harvest server process requires 15 MB of RAM.
Locate your II_DATABASEdatadefaultmdb directory.
II_DATABASE is your II_DATABASE setting in Ingres. By default, II_DATABASE is same as the Ingres installation directory, II_SYSTEM. To find the II_DATABASE setting, check the II_SYSTEMingres/filessymbol.tbl file.
Find and record the size of that directory.
Ensure that amount of free disk space on your computer is equal to six times the size of the mdb directory plus 1 GB. For example:
Ingres Server (local Ingres database)
The Ingres server on Windows requires the following:
Important! The AllFusion Harvest express installation sets the Ingres transaction log file size to 512 MB. The total file size that the AllFusion Harvest server can process at any one time is approximately one-fourth of the transaction log size. Therefore, if you use the express installation, the total file size the AllFusion Harvest server can process at any one time is approximately 128 MB. If this file size does not meet your requirements, you should either use the custom installation (see the CA Software Change Manager Installation Guide) or set the transaction log size to a sufficiently higher value after installation (see the Ingres System Administrator Guide).
For further information about Ingres, see your Ingres documentation.
Ingres Client only (Remote Ingres Database)
If you plan to use a remote Ingres database and install only the Ingres client on the Harvest server computer, the Ingres requirements are:
Oracle
Oracle requires the following:
For more information about Oracle, see your Oracle documentation.
Microsoft SQL Server
Microsoft SQL Server requires the following:
For more information about Microsoft SQL Server, see your Microsoft SQL Server documentation.
Unicenter Software Delivery Integration
To deploy software on target computers and computer groups using the Unicenter Software Delivery Integration feature of Harvest, you must have the CA solution Unicenter Software Delivery r11 installed and configured according to the instructions and requirements in the Unicenter Software Delivery r11 documentation. The Harvest server and Unicenter Software Delivery server can be running on any supported platform; the two servers are not required to be running on the same platform. For example, the Harvest server can be running on a Windows platform that supports it, while the Unicenter Software Delivery server can be running on a Linux platform that supports it.
To set up AllFusion Harvest to use Unicenter Software Delivery Integration, you configure the AllFusion Harvest server while or after installing it. This configuration does not add any additional hardware or software prerequisites to the server or any other AllFusion Harvest component.
For details about setting up Unicenter Software Delivery Integration during the AllFusion Harvest server installation, see the CA Software Change Manager Installation Guide. For details after this installation, see the CA Software Change Manager Administrator Guide. For details about using Harvest and Unicenter Software Delivery together to deploy software, see the CA Software Change Manager Administrator Guide.
Important! For a very important step required to start using Unicenter Software Delivery Integration, see Administrator Guide--Unicenter Software Delivery Integration in Documentation Changes in this readme.
Because of the cross-platform support that both AllFusion Harvest and Unicenter Software Delivery provide, you can use them together to deploy software on any platform that the Unicenter Software Delivery agent supports. For details about these platforms, see your Unicenter Software Delivery documentation.
Agent and Client, Installed Locally, Not Shared
When the AllFusion Harvest client on Windows is installed locally and is not shared, it requires the following hardware and software. These requirements also apply to the AllFusion Harvest agent on Windows.
HSDK
On Windows, the HSDK is installed automatically whenever you install any AllFusion Harvest component, except Database and Documentation, 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 CA Software Change Manager Installation Guide.
The Harweb computer requires the following to be installed locally:
If the size of the mdb directory is 1 GB, then the space requirement for the upgrade is (1 GB x 6) + 1 GB = 7 GB.
If the size of the mdb directory is 2 GB, then the requirement is (2 GB x 6) + 1 GB = 13 GB.
Ingres version 3.0.3
Important! At publication time, using Harvest with an Ingres database requires the Ingres version 3.0.3. Any updates to this requirement after publication time will be posted by Customer Support on https://support.ca.com. While installing the AllFusion Harvest server, you can optionally install locally the Ingres client only or the Ingres server (which includes the Ingres client); for details, see the CA Software Change Manager Installation Guide. For information about using Harvest with a remote Ingres database, see the next section, Ingres Client Only (Remote Ingres Database).
A minimum 512 MB of RAM for running Ingres
A minimum 1 GB of RAM for running both AllFusion Harvest and Ingres
3 GB of disk space
Approximately 1 to 10 GB of disk space to account for database growth
512 MB to 2 GB of disk space for the Ingres transaction log
Ingres version 3.0.3
Important! At publication time, using Harvest with an Ingres database requires the Ingres version 3.0.3. Any updates to this requirement after publication time will be posted by Customer Support on https://support.ca.com. While installing the AllFusion Harvest server, you can optionally install locally the Ingres client only or the Ingres server (which includes the Ingres client); for details, see the CA Software Change Manager Installation Guide. To install and use Ingres version 3.0.3 remotely (on a different computer than the Harvest server), you must install Harvest and the Ingres server separately; for details, see the Tech Doc Setting Up Harvest r7.1 with a Remote Ingres Database on https://support.ca.com.
An Intel Pentium processor (Pentium 4 recommended)
A minimum 20 MB of disk space for installing the Ingres client
A minimum 512 MB of RAM for running AllFusion Harvest
A minimum 1 GB of RAM for running both AllFusion Harvest and Ingres
110 MB of disk space for temporary use during the installation process
At least 70 MB of disk space for the AllFusion Harvest product files
Oracle 9.2.0 EE, 9.2.0 SE, 10g, or 10g Release 2.
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.
If you want to install the AllFusion Harvest server with a remote Oracle database, see the CA Software Change Manager Installation Guide.
Microsoft SQL Server 2000 or 2005.
Minimum 50 MB of disk space to hold Harvest data.
If you want to install the AllFusion Harvest server with a remote Microsoft SQL Server database, see the CA Software Change Manager Installation Guide.
An Intel Pentium processor (Pentium 4 recommended).
At least 60 MB of disk space for the AllFusion Harvest product files.
At least 512 MB of RAM.
Network connection using the TCP/IP protocol to an AllFusion Harvest server running UNIX, Linux or Windows.
110 MB of disk space for temporary use during the installation process.
Apache Tomcat 4.1.29, 4.1.30, 5.0.25, 5.5.4, 5.5.7, 5.5.9, 5.5.12, or 5.5.15. Tomcat is available for free. For details, see the Apache website, 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 website, http://sun.com.
IBM WebSphere Application Server 5.0 or 5.1. These editions are fully J2EE-compliant. These editions also provide web server support and servlet support for Harweb. For details, see the IBM website, http://ibm.com.
JBoss Application Server 4.0.3. JBoss AS is J2EE-certified and is available for free. For details, see the JBoss website, http://jboss.org.
The AllFusion Harvest client (command line utility)
One of the following versions of Java SDK Standard Edition:
Harweb requires one of the following web browsers:
If the AllFusion Harvest database is running on Microsoft SQL Server, Harweb requires the manual download and installation of one of the Microsoft SQL Server JDBC drivers, as follows:
3.2 UNIX and Linux

This section describes the system requirements for the AllFusion Harvest components on UNIX and Linux.
All Clients
On UNIX and Linux, the AllFusion Harvest command line utilities serve as the AllFusion Harvest clients. The AllFusion Harvest client (command line utility) requires 15 MB of disk space.
All Servers
The AllFusion 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.
Requirements for Linux computers include the following:
Requirements for UNIX computers include the following:
Note: The AllFusion Harvest installation includes the following CA shared components: CA Licensing (Lic98), CAI/PT ODBC, Enterprise Communicator (PEC), and CA Cryptographic Engine (CACE). A root user account is required to install CA Licensing (Lic98). The other CA shared components can be installed to a user-specified location, which may not require a root account.
AllFusion Harvest Server with an Ingres Database (New Installation)
The AllFusion Harvest server computer with a local Ingres database requires the following:
AllFusion Harvest Server with a Local Ingres Database (Upgrade)
If you are upgrading an existing Harvest server with a local Ingres database, the same requirements as a new installation apply, except that you may require more disk space. To determine the amount of disk space you need, do the following:
1.4.2_04, 1.4.2__05, 1.4.2__06, 1.4.2__07
1.5 (also named 5.0)
1.5.0_01 (also named 5.0 Update 1)
1.5.0_02 (also named 5.0 Update 2)
1.5.0_06 (also named 5.0 Update 6)
Microsoft Internet Explorer 6.0
Mozilla 1.4 to 1.7
Mozilla Firefox 1.5
If the AllFusion Harvest database is installed on Microsoft SQL Server 2000, use either the Microsoft SQL Server 2000 JDBC driver or the Microsoft SQL Server 2005 JDBC driver.
If the AllFusion Harvest database is installed on Microsoft SQL Server 2005, use the Microsoft SQL Server 2005 JDBC driver.
An Intel Pentium processor (Pentium 4 recommended).
A minimum 128 MB of main memory.
15 MB of virtual memory for each AllFusion Harvest server process.
A local or remote database running a supported version of Oracle or Ingres. Details about each database's requirements are provided in this section.
IBM AIX: 1.65 GHz, 512 MB RAM.
HP-UX: 650 MHz, 512 MB RAM.
Sun Solaris: 1.28 GHz, 512 MB RAM.
15 MB of virtual memory for each AllFusion Harvest server process.
A local or remote database running a supported version of Oracle or Ingres. Details about Oracle's requirements are provided in this section.
Disk Space: 6 GB recommended.
Memory: 1 GB RAM, minimum. Each Harvest server process requires 15 MB of RAM.
Locate your II_DATABASE/data/default/mdb directory.
II_DATABASE is your II_DATABASE setting in Ingres. By default, II_DATABASE is same as the Ingres installation directory, II_SYSTEM. To find the II_DATABASE setting, check the II_SYSTEM/ingres/files/symbol.tbl file.
Find and record the size of that directory.
Ensure that amount of free disk space on your computer is equal to six times the size of the mdb directory plus 1 GB. For example:
Ingres Server (local Ingres database)
The Ingres server on Windows requires the following:
Important! The AllFusion Harvest express installation sets the Ingres transaction log file size to 512 MB. The total file size the AllFusion Harvest server can process at any one time is approximately one-fourth of the transaction log size. Therefore, if you use the express installation, the total file size the AllFusion Harvest server can process at any one time is approximately 128 MB. If this file size does not meet your requirements, you should either use the custom installation (see the CA Software Change Manager Installation Guide) or set the transaction log size to a sufficiently higher value after installation (see the Ingres System Administrator Guide).
For more information about Ingres, see your Ingres documentation.
Ingres database files cannot be stored in a Reiser file system ("ReiserFS")
Important! If you plan to install AllFusion Harvest and Ingres on Novell SUSE LINUX, the GCC (GNU C Compiler) must be installed before you install Harvest!
Ingres Client Only-for Remote Ingres Database
If you plan to use a remote Ingres database and install only the Ingres client on the Harvest server computer, the Ingres requirements are:
Oracle
Oracle requires the following:
For more information about Oracle, see your Oracle documentation.
Unicenter Software Delivery Integration
To deploy software on target computers and computer groups using the Unicenter Software Delivery Integration feature of Harvest, you must have the CA solution Unicenter Software Delivery r11 installed and configured according to the instructions and requirements in the Unicenter Software Delivery r11 documentation. The Harvest server and Unicenter Software Delivery server can be running on any supported platform; the two servers are not required to be running on the same platform. For example, the Harvest server can be running on a UNIX or Linux platform that supports it, while the Unicenter Software Delivery server can be running on a Windows platform that supports it.
To set up AllFusion Harvest to use Unicenter Software Delivery Integration, you configure the AllFusion Harvest server while or after installing it. This configuration does not add any additional hardware or software prerequisites to the server or any other AllFusion Harvest component.
For details about setting up Unicenter Software Delivery Integration during the AllFusion Harvest server installation, see the CA Software Change Manager Installation Guide. For details after this installation, see the CA Software Change Manager Administrator Guide. For details about using Harvest and Unicenter Software Delivery together to deploy software, see the CA Software Change Manager Administrator Guide.
Important! For a very important step required to start using Unicenter Software Delivery Integration, see Administrator Guide--Unicenter Software Delivery Integration in Documentation Changes in this readme.
Because of the cross-platform support that both AllFusion Harvest and Unicenter Software Delivery provide, you can use them together to deploy software on any platform that the Unicenter Software Delivery agent supports. For details about these platforms, see your Unicenter Software Delivery documentation.
Sun Solaris Servers
The AllFusion Harvest server on Sun Solaris requires approximately 100 MB of disk space for the AllFusion Harvest product files, Lic98, CACE, PEC, and CAI/PT ODBC.
For Solaris 8, only, AllFusion Harvest on Solaris requires the latest Sun patches for SUNWlibC and SUNWlibCx. The patches installed must be at least the following versions:
If the following command does not return libCrun.so.1 and libCstd.so.1, your system needs to be patched. ls /usr/lib/libC*
To obtain a patch, go to the Sun website, http://sun.com.
To determine what version of a patch is already installed on your computer, enter the following command: showrev -p | grep patch#
where patch# is the number of the patch, for example, 108434 or 108436. This command returns the version of the patch.
IBM AIX Servers
The AllFusion Harvest server on IBM AIX requires approximately 200 MB of disk space for the AllFusion Harvest product files, Lic98, CACE, PEC, and CAI/PT ODBC.
AllFusion Harvest on AIX requires IBM C Set ++ Runtime for AIX at level 7.0.0.0 or higher. To check what version of C Set ++ Runtime for AIX is installed on your server, enter the following command at the command line:

$ lslpp -L xlC.rte
Something similar to the following should be returned:
```
Fileset                Level  State  Type  Description (Uninstaller)
--------------------------------------------------------------------
xlC.rte              7.0.0.0    C     F    C Set ++ Runtime
```
The Level must be 7.0.0.0 or higher with a State of C for Committed. If you do not have at least level 7.0.0.0 of C Set ++ Runtime for AIX installed, you must upgrade your AIX runtime libraries before running Harvest.
For more information on IBM C Set ++ Runtime for AIX, go to the IBM website, http://ibm.com.
HP-UX Servers
The AllFusion Harvest server on HP-UX requires approximately 200 MB of disk space for the AllFusion Harvest product files, Lic98, CACE, PEC, and CAI/PT ODBC.
Novell SUSE LINUX Enterprise Server for x86 Servers
The AllFusion Harvest server on Novell SUSE LINUX Enterprise Server 8 or 9 for x86 requires approximately 150 MB of disk space for the AllFusion Harvest product files, Lic98, CACE, PEC, and CAI/PT ODBC.
The Linux installation program 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.

3.3 Harvest Client and Agent on Novell SUSE LINUX Enterprise Server for s/390

The AllFusion Harvest client (command line utility) and agent on Novell SUSE LINUX Enterprise Server 8 or 9 for s/390 run on s/390 and require the following:
3.4 ISPF Client

The ISPF Client runs on zSeries hardware and requires the following:
Harweb
Harweb requires 65 MB of disk space.
Harweb requires one of the following servlet engines. For instructions to install Harweb and each of these servlet engines, see the CA Software Change Manager Installation Guide.
The Harweb computer requires the following to be installed locally:
If the size of the mdb directory is 1 GB, then the space requirement for the upgrade is (1 GB x 6) + 1 GB = 7 GB.
If the size of the mdb directory is 2 GB, then the requirement is (2 GB x 6) +1 GB = 13 GB.
Ingres version 3.0.3.
Important! At publication time, using AllFusion Harvest with an Ingres database requires the Ingres version 3.0.3. Any updates to this requirement after publication time will be posted by Customer Support on https://support.ca.com. While installing the AllFusion Harvest server, you can optionally install locally the Ingres client only or the Ingres server (which includes the Ingres client); for details, see the CA Software Change Manager Installation Guide. For information about using AllFusion Harvest with a remote Ingres database, see the next section, Ingres Client Only-for Remote Ingres Database.
A minimum 512 MB of RAM for running Ingres.
A minimum 1 GB of RAM for running both AllFusion Harvest and Ingres.
3 GB of disk space.
Approximately 1 to 10 GB of disk space to account for database growth.
512 MB to 2 GB of disk space for the Ingres transaction log.
Ingres runs on Novell SUSE LINUX Enterprise Server. For important related requirements, see Operating System Support in this readme.
Ingres version 3.0.3
Important! At publication time, using AllFusion Harvest with an Ingres database requires the Ingres version 3.0.3. Any updates to this requirement after publication time will be posted by Customer Support on https://support.ca.com. While installing the AllFusion Harvest server, you can optionally install locally the Ingres client only or the Ingres server (which includes the Ingres client); for details, see the CA Software Change Manager Installation Guide. To install and use Ingres version 3.0.3 remotely (on a different computer than the Harvest server), you must install AllFusion Harvest and the Ingres server separately; for details, see the Tech Doc Setting Up Harvest r7.1 with a Remote Ingres Database on https://support.ca.com.
A minimum 20 MB of disk space for installing Ingres client
A minimum 128 MB of RAM for running Ingres client
A minimum 640 GB of RAM for running both AllFusion Harvest and Ingres client
Oracle 9.2.0 EE, 9.2.0 SE, 10g, or 10g Release 2
If the Oracle database resides on a different computer than the Harvest server, SQL*Net is required
Approximately 210 MB for the Oracle tablespaces
SUNWlibC 32-bit requires 108434-17
SUNWlibCx 64-bit requires 108435-17
Approximately 45 MB of disk space for the agent, CA Cryptographic Engine (CACE), and Enterprise Communicator (PEC)
Approximately 30 MB of disk space for the client
TSO region size of 4096
550 tracks of temporary space
620 tracks for permanent data sets
2 cylinders on a 3390 device
TCP/IP protocol
C ++ Runtime Libraries
ISPF
One of the following: eTrust CA-Top Secret Security (eTrust CA-Top Secret), eTrust CA-ACF2 Security (eTrust CA-ACF2), or IBM RACF
Apache Tomcat 4.1.29, 4.1.30, 5.0.25, 5.5.4, 5.5.7, 5.5.9, 5.5.12, or 5.5.15. Tomcat is available for free. For details, see the Apache website, 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 website, http://sun.com.
IBM WebSphere Application Server 5.0 or 5.1. These editions are fully J2EE-compliant. These editions also provide web server support and servlet support for Harweb. For details, see the IBM website, http://ibm.com.
JBoss Application Server 4.0.3. JBoss AS is J2EE-certified and is available for free. For details, see the JBoss website, http://jboss.org.
The AllFusion Harvest client (command line utility)
CA Cryptographic Engine (CACE)
One of the following versions of Java SDK Standard Edition:
If the AllFusion Harvest database is running on Microsoft SQL Server, Harweb requires the manual download and installation of one of the Microsoft SQL Server JDBC drivers, as follows:
3.5 Web Servers

Note: Ensure that the version of Java SDK Standard Edition you install is supported by the web server you plan to install.
Microsoft IIS
Sample Reports requires Microsoft Internet Information Server (IIS) version 5.0 or 6.0.
Sun Java System Web Server
Harweb supports Sun Java System Web Server Enterprise Edition 6.0 and 6.1.
Note: This edition is supported as both web server and J2EE platform for Harweb.
IBM WebSphere
Harweb requires IBM WebSphere Application Server 5.0 or 5.1.
Note: WebSphere Application Server includes an HTTP web server based on Apache Webserver and is fully J2EE compliant. This edition also provides web server and servlet support for Harweb. For details, see the IBM website, http://ibm.com.

3.6 JBoss

JBoss Application Server 4.0.3. JBoss AS is J2EE-certified and is available for free. For details, see the JBoss website, http://jboss.org.

3.7 LDAP Server

At publication time, Harvest supports LDAP authentication on the following LDAP servers:
3.8 Security

By default, AllFusion Harvest agents that have LDAP authentication installed and configured use Transport Layer Security (TLS) to communicate with the LDAP server. However, you can optionally configure the agent to use no encryption mechanism. For details, see the CA Software Change Manager Administrator Guide.

3.9 TestDirector Integration

The AllFusion Harvest TestDirector Integration option must be installed on the Mercury TestDirector server computer. Before installing TestDirector Integration, ensure that the following components are installed:
1.4.2_04, 1.4.2__05, 1.4.2__06, 1.4.2__07
1.5 (also named 5.0)
1.5.0_01 (also named 5.0 Update 1)
1.5.0_02 (also named 5.0 Update 2)
1.5.0_06 (also named 5.0 Update 6)
Enterprise Communicator (PEC)
Mozilla 1.4 to 1.7 web browser or Mozilla Firefox 1.5
If the AllFusion Harvest database is installed on Microsoft SQL Server 2000, use either the Microsoft SQL Server 2000 JDBC driver or the Microsoft SQL Server 2005 JDBC driver.
If the AllFusion Harvest database is installed on Microsoft SQL Server 2005, use the Microsoft SQL Server 2005 JDBC driver.
Microsoft Active Directory (bundled with Windows 2000 Server or Windows 2003 Server)
Novell eDirectory Server 8.7.3
IBM Tivoli Directory Server version 5.2
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 AllFusion Harvest integration require the Java JRE 1.4.2_04. When using TestDirector or AllFusion Harvest TestDirector Integration, you must have the Java JRE active in the path prior to installation.
Visual C++ 6.0.
One of the following:
For details about setting up Harvest to work with TestDirector, see the CA Software Change Manager Integration Tools User Guide.

3.10 Version Control Interface (VCI)

Before installing Version Control Interface (VCI), ensure that Visual Basic 6.0 Enterprise Edition is installed. This application is certified for supporting the Microsoft Common Source Code Control (SCC) Interface.
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 select 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.
Important! The CA support policy dictates that CA solutions cannot support a third-party product whose vendor has stabilized (dropped support for) that product. Because Microsoft has stabilized Visual C++ 6.0 Enterprise Edition, AllFusion Harvest r7.1 does not support that product. However, in an effort to allow Harvest VCI users additional time to upgrade to Microsoft Visual Studio .NET 2003 and 2005, Harvest r7.1 continues to provide access to an unsupported integration with Microsoft Visual C++ 6.0 Enterprise Edition. AllFusion Harvest r7.1 is the final release to include this integration.
VCI supports the following applications.
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.
Visual Studio .NET 2002
Visual Studio .NET 2003 and 2005
Important! In AllFusion Harvest r7.1, Visual Studio .NET 2005 is certified for use with SCC API 1.2 only! However, in an effort to allow AllFusion Harvest VCI users additional time to upgrade to SCC API 1.2, Harvest r7.1 provides access to an unsupported integration of Visual Studio .NET 2005 with SCC API 1.1. When you install VCI, Harvest selects a version of SCC API based on the Visual Studio .NET version installed in your computer. For details, see the CA Software Change Manager Version Control Interface User Guide.
Sybase PowerBuilder 8.0.3, 9.0, and 10.0
Rational Rose:
Before using the VCI, perform the setup tasks in the CA Software Change Manager Version Control Interface User Guide.

3.11 Sample Reports

This section describes the system requirements for the AllFusion Harvest Sample Reports component.
Database Server
The database server requires CA Software Change Manager Server r7.1.
A computer running Sample Reports locally requires the following software:
Server
A server hosting Sample Reports on a network requires the following software:
Client
A client accessing the host server for Sample Reports requires a Windows operating system that supports the following:
4.0 Installation Considerations

For instructions to install AllFusion Harvest r7.1, see the CA Software Change Manager Installation Guide.

This section contains miscellaneous installation considerations for AllFusion Harvest r7.1.
Notes:
4.1 Security Concerns

PR2937: On UNIX and Linux, installing the AllFusion Harvest components requires only system user access (the system user named harvest). However, installing the required CA shared components for the first time requires root user access. The CA shared components required by AllFusion Harvest are CA Licensing (Lic98), CA Cryptographic Engine (CACE), CAI/PT ODBC, and Enterprise Communicator (PEC).
After these CA shared components have been installed once, only system user access (the system user named harvest) is required to update, delete, or re-install them. The only exception is Lic98, which always requires root access to install, update, delete, or re-install.
You must also have root access to install the AllFusion Harvest server with Ingres. This requirement applies to custom and express installations.

4.2 For Ingres Users-Windows

PR4045: On Windows, if you install Ingres while installing the AllFusion Harvest server, do not use an operating system user named harvest to perform the installation.
This warning applies to both the express and custom installations of the AllFusion Harvest server documented in the chapter "Upgrading or Installing the Server on Windows" in the CA Software Change Manager Installation Guide.
For Microsoft SQL Server Users
Important! If your DBMS is Microsoft SQL Server and you want to create a Harvest database using the Database Configuration Utility, you need to ensure that your Windows operating system user ID is granted the system administrator role in Microsoft SQL Server.

4.3 For Ingres Users-Novell SUSE LINUX Enterprise Server

Using AllFusion Harvest with Ingres is supported on Novell SUSE LINUX Enterprise Server only , not on any other Linux platforms. Using AllFusion Harvest with Ingres is not supported on UNIX.
As noted earlier in PR2937 under Security Concerns, you must have root access to install the AllFusion Harvest server with Ingres (custom or express).
Ensuring Required File Permissions for Ingres
While installing AllFusion Harvest with Ingres on Novell SUSE LINUX Enterprise Server, after accepting the license agreement, you may receive an error message similar to the following:
```
System user ingres has been created but no password has been set.
Please set the password to enable login for this user.
Response file is not readable by user : ingres
    II_RESPONSE_FILE=/root/harvest/harvest/install/ingrestmp.rsp
...
 execution of ca-ingres-EI-3.0.1-109 script failed, exit status 5
 ca-ingres is not installed under /opt/CA/IngresEI
 Aborting...
... 
```
The message may indicate that several Ingres scripts have failed and aborted.
The error is issued because the ingres user does not have the required access rights. For the installation to complete successfully, the ingres user must exist and must have read and execute permission to the parent folders of the AllFusion Harvest installation script. If the ingres user does not exist, the installation creates it automatically. However, if you receive the previous error message, do the following to fix the problem:
GCC Compiler Required
Important! If you plan to install AllFusion Harvest and Ingres on Novell SUSE LINUX, the GCC (GNU C Compiler) must be installed before you install Harvest! For more information, see the section For Novell SUSE LINUX Enterprise Server for x86 Users.
ext3 File System Required
If you are using Ingres on Novell SUSE LINUX Enterprise Server, you must use an ext3 file system. Ingres database files cannot be stored in a Reiser file system (ReiserFS).
Changing Ownership of the hsvr.dfo File
PR4052: After you have completed a custom or express installation of the AllFusion Harvest server, the root user owns the .hsvr.dfo file. Consequently, the AllFusion Harvest server cannot read the .hsvr.dfo file. Therefore, the AllFusion Harvest server cannot start and you cannot run the database configuration utility.
To fix this problem, after the installation has completed, while logged on as the root user, run the following commands to change the ownership of the .hsvr.dfo file:

chown harvest:harvest .dfo
For Local Ingres Databases Running on Linux
PR5402: If you plan to use a local Ingres database (on the same computer as the Harvest server) and you installed CAI/PT ODBC before you installed the Ingres server, do the following: In the ODBC_HOME/lib directory, rename libiiodbcdriver.1.so file to xxlibiiodbcdriver.1.so. For example, enter the following commands:

mv libiiodbcdriver.1.so xxlibiiodbcdriver.1.so
Important! If this step applies to your installation but is skipped, the Harvest installation may fail, or Harvest may not be able to connect to the Ingres database!

4.4 For Oracle Users

Important! If you are upgrading to Harvest r7.1, before upgrading the Harvest server, ensure that you are running a version of Oracle supported by Harvest r7.1. Users of Oracle 8i (or lower) must upgrade to a supported Oracle version! For a list of supported versions, see System Requirements.
Important! You must install or upgrade Oracle before running the Harvest database configuration utility!
Do not Use Configdsn
Important! If you are using Oracle, do not use configdsn to set up your AllFusion Harvest database. You must use the database configuration utility instead. For instructions to use it, see the chapter "Installing, Configuring, and Maintaining Your Database" in the CA Software Change Manager Installation Guide.

4.5 For Microsoft SQL Server Users

Important! You must install Microsoft SQL Server before running the Harvest database configuration utility!
Specify Language Settings Very Carefully
Important! If you plan to run your Harvest database on Microsoft SQL Server, be very careful to specify the language settings correctly for your environment when you install Microsoft SQL Server. For example, if you plan to run your Harvest database on Microsoft SQL Server with Finnish_Swedish collation, you must select the 'Accent-Sensitive' collation option when you install SQL Server; if you do not select this option, critical HServer SQL will fail with unexpected ODBC errors! For more information about installing SQL Server, see your SQL Server documentation.

4.6 For Novell SUSE LINUX Enterprise Server for s/390 Users

If you are using Novell SUSE LINUX Enterprise Server for s/390 and you encounter an error regarding a missing libstdc++-libc6.1-2.so.3 file, you must install the gcc-c++-2.95.2-4.s390.rpm package. This rpm package may be provided on the Novell SUSE LINUX Enterprise Server installation media. If necessary, download this rpm package from ( http://linux.s390.org/ or http://rpmfind.net/ ) and install it. For instructions to install or update an rpm package, see the rpm man pages.

4.7 For Novell SUSE LINUX Enterprise Server for x86 Users

If you are using Novell SUSE LINUX Enterprise Server for x86 and you encounter an error regarding a missing libgcc_so.1 or libstdc++.so.5 file, install one of the following packages:
These rpm packages may be provided on the Novell SUSE LINUX Enterprise Server installation media. If necessary, download these rpm packages from the SUSE website ( http://novell.com/linux/suse or http://rpmfind.net/ ) and install them. Doing so is required if you are using an emulator to connect from a Windows computer to a /linux_base port. For instructions to install or update an rpm package, see the rpm man pages.

4.8 For Red Hat Linux Users

If you are using Red Hat Enterprise Linux Advanced Server 3.0 or 4.0 or Red Hat Enterprise Linux Enterprise Server 3.0 or 4.0 and you encounter an error regarding a missing *.so file, install the corresponding rpm package for your Red Hat operating system. For example:
Typically, the rpm packages for your Red Hat operating system are provided on the installation media for your Red Hat operating system. However, if necessary, you can download these rpm packages from the Red Hat website ( http://redhat.com/ or the RPM website http://rpmfind.net/ ). After acquiring the rpm packages you need, install them. Doing so is required if you are using an emulator to connect from a Windows computer to a /linux_base port. For instructions to install or update an rpm package, see the rpm man pages.
Note: AllFusion Harvest is built with the libraries in the libgcc-3.2.3-20.i386.rpm and libstdc++-3.2.3-20.i386.rpm packages.

4.9 For Users Who Upgrade any Harvest Component on Windows

On a Windows computer, when you install a Harvest r7.1 component or upgrade an existing Harvest component to Harvest r7.1, any existing installation of Enterprise Communicator (PEC) on that computer is automatically upgraded to PEC 4.6.1, the PEC version bundled with Harvest 7.1. However, on rare occasions, when you install or upgrade Harvest on a Windows computer, an existing PEC installation may not be upgraded automatically as it should be.
To check the PEC version, search for the %RTHOME%standardversion.txt file and open it. If the version shown in this file is lower than 4.6.1, run the PEC installation manually to upgrade PEC. To run the PEC installation manually, do the following:
4.10 For Harweb Users Running Sun Java System Web Server

PR4637: Harweb may not work correctly if you use Sun Java System Web Server 6.1 and Sun Solaris 10 together. As a workaround, try the following:
4.11 For Harweb Users Running WebSphere Application Server on UNIX or Linux

On UNIX or Linux, when you attempt to deploy Harweb on WebSphere Application Server 5.x, WebSphere Application Server may issue an OutOfMemoryError exception error and abort the attempt. If this problem occurs, perform the following steps:
After performing these steps, attempt to deploy Harweb again.
For instructions to install and deploy Harweb, see the CA Software Change Manager Installation Guide. For more information about the WebSphere Application Server memory error, see the IBM website, http://ibm.com.

4.12 For Harweb Users with Microsoft SQL Server

As explained in Microsoft bug FDBK45212, stored procedures fail when you attempt to use the Microsoft SQL Server 2005 JDBC driver with a Microsoft SQL Server 2000 database. Consequently, Harweb will not work correctly in this environment. For example, you may be able to install Harweb successfully in this environment but may not be able to create the Harvest repository or may encounter other severe errors. As a workaround, do one of the following:
4.13 Sample Reports

You must install the AllFusion Harvest r7.1 server and client before you install Sample Reports. For instructions to install AllFusion Harvest r7.1, see the CA Software Change Manager Installation Guide.
For instructions to install and use Sample Reports, see the CA Software Change Manager Sample Reports User Guide.

4.14 Sample Reports and Ingres

If you are using Sample Reports and Ingres, you must set up an ODBC data source using the System DSN tab of the Windows ODBC Data Source Administrator. For details, see the chapter "Installing AllFusion Harvest Sample Reports" in the CA Software Change Manager Sample Reports User Guide. In that chapter, when performing Step 5 in Setup for Ingres (Local), to set up the ODBC data source for a local Ingres user, add the group name harvest_rep in the Group field of the System DSN tab.

4.15 CA Cryptographic Engine (CACE) on Sun Solaris 8

To use the CA Cryptographic Engine (CACE) on Sun Solaris 8, you must install Patch 108434-14 and its dependent patch, 109147-08. To obtain these patches, go to the Sun website, http://sun.com.

4.16 TestDirector Integration

Mercury TestDirector Integration is an optional component on the AllFusion Harvest r7.1 client custom installation. For instructions to install TestDirector Integration, see the CA Software Change Manager Installation Guide.
Important! If the AllFusion Harvest client on the TestDirector server computer is uninstalled and reinstalled in another location after TestDirector data has been checked in to the AllFusion 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 AllFusion Harvest installation is moved, a copy of htdvcElement.dtd must remain in its original location.

4.17 CA Licensing (Lic98)

All Windows, UNIX, and Linux versions of AllFusion Harvest r7.1 have been updated to the latest version of CA Licensing (Lic98) . By default, the latest Lic98 installation now creates /opt/CA/SharedComponents/ca_lic and /opt/CA/SharedComponents/lib directories for the licensing files.
The installation creates $CASHCOM/ca_lic and $CASHCOMP/lib directories that contain the Lic98 files. The default location for the $CASHCOMP directory is /opt/CA/SharedComponents.
If you are installing on a computer that has never had Lic98 installed and you want to change this location, change the $CASHCOMP environment variable from the default setting (/opt/CA/SharedComponents) to a new path name before running the installation. If the $CASHCOMP environment variable is not set, you can set it according to the instructions provided by your UNIX or Linux operating system.
Important! After Lic98 is installed on a computer, the Lic98 installation directory cannot be changed, even by updating the $CASHCOMP variable described in the previous section, CA Licensing (Lic98).

4.18 For RACF Users

For instructions to establish RACF security, see the IBM z/OS Unix System Services Planning Guide. This guide is available from the IBM website at http://ibm.com.
The AllFusion Harvest z/OS agent uses USS and requires a valid OMVS segment for users using and starting the agent. If users have no OMVS segment defined, a default OMVS segment must be defined. The z/OS agent issues authorization functions for users logged in to it.

4.19 Plug-in External Merge/Compare Tools

AllFusion Harvest supports the following external difference/merge tools, some of which can perform a three-way merge:
For more information on these tools, see the CA Software Change Manager User Guide.

5.0 General Considerations

For a list and brief description of new and changed features supplied by AllFusion Harvest r7.1, see the CA Software Change Manager Release Summary.

5.1 CA Management Database (MDB)

The CA Management Database (MDB) is the standard database schema for storing CA product data. The MDB is installed when you install and run a CA solution that supports the MDB for the DBMS and the operating system that you are using. For Harvest, the MDB is installed when you do either of the following:
Important! Do not delete any table in the MDB, except Harvest custom form tables; if you delete any other MDB table, the data in the MDB may become corrupted!
For details about the MDB, see the MDB Overview.

5.2 New -nvf Option for the hco Command Utility

The hco command line utility includes a new option, -nvf. This new option enables you to specify how Harvest handles "file not found" errors that occur when the hco command is running. For details, see Documentation Changes.

5.3 Change in How the hco Command Utility Processes Read-only Files

Important! The method that the hco command utility uses to determine whether to replace read-only files at check-out time has changed in Harvest r7.1. This change may impact users of the hco command who previously relied on the related Administrator application setting to determine whether to replace read-only files at check out. Check your hco commands on both the command line and in the scripts to ensure that this change does not cause the commands to fail or produce unexpected results. If necessary, update your hco commands to re-produce the expected results. For details, see PR2792 in Known Issues.

5.4 Performance Management

AllFusion Harvest includes several configuration options that you can customize for optimal performance in your AllFusion Harvest environment. For options to configure your AllFusion Harvest server, broker, and other components for best performance, see the CA Software Change Manager Administrator Guide. Key parameters that can directly affect performance are listsize and commsize. Listsize specifies the number of records to retrieve from the database and send across the network at the same time. Commsize specifies the size of the data buffer sent between the agent and the server during check in and check out.

5.5 Accessing Harvest Objects using Visual Basic Scripts

PR3291: In AllFusion Harvest r7.1, you use Visual Basic scripts to access COM SDK objects from the task bar and forms in the AllFusion Harvest Workbench or Administrator application. To write these Visual Basic scripts, use the Component Object Model SDK (COM SDK). For instructions, see the CA Software Change Manager COM SDK Reference.
In a Visual Basic script for accessing the COM SDK objects from the task bar or forms, use the following sample code as a starting point:
```
Set Project = Application.Project
Set objHarvest = Project.GetHarvestObject()
If (objHarvest Is Nothing) Then
     MsgBox "Could not get Harvest object"
   Exit Function
End If
```
After you code the previous lines, you can access any COM SDK object documented in the CA Software Change Manager COM SDK Reference.
```
Set objContext = objHarvest.GetContext()
If (objContext Is Nothing) Then
     MsgBox "Could not get context object"    Exit Function
End If
```
After completing your script, you can test it and run it in the Workbench or Administrator application, from the task bar or a form.
Notes:
5.6 Published Fixes

For all published fixes for AllFusion Harvest, see the Published Solutions provided by Customer Support on https://support.ca.com.

6.0 Documentation Changes

This section provides updates to the AllFusion Harvest documentation that became known after the documentation was published.

6.1 Administrator Guide-Form Tables in SQL Server

In the CA Software Change Manager Administrator Guide, in the chapter "Creating and Converting Form Types," update Add the Form Table to Your Harvest Database with the following instructions for SQL Server:
Rational Rose 2003
Rational Rose XDE Developer for Java
Rational Rose XDE Developer for .NET
Rational Rose XDE Developer for Visual Studio
CleverPath Forest & Trees 7.0 (required to customize reports, optional to view reports)
CleverPath Forest & Trees Runtime Option 7.0 (required to view reports)
Oracle Client 9.2.0 EE, 9.2.0 SE, 10g, or 10g Release 2; or Ingres client version 3.0.3; or Microsoft SQL Server client 2000 or 2005
CleverPath Forest & Trees 7.0 (required to customize reports, optional to view reports)
CleverPath Forest & Trees Runtime Option 7.0
Remote Data Server Components
Microsoft Internet Information Services (IIS) 5.0 or 6.0
Microsoft Data Services
CleverPath Portal 4.01 (optional)
Windows Authentication Component (optional)
Oracle Client 9.2.0 EE, 9.2.0 SE, 10g, or 10g Release 2; or Ingres version 3.0.3; or Microsoft SQL Server 2000 or 2005
CleverPath Forest & Trees Runtime Option 7.0
Microsoft Internet Explorer 6.0
AllFusion Harvest r7.1 is cumulative.
For additional installation-related information in this readme, see Installation in Known Issues and Installation Guide in Documentation Changes.
Before running the express installation again, check to see if the ingres user already exists.
If the ingres user does already exist, ensure that it (or the user group to which it belongs) has read and execute permission to the parent folders of the AllFusion Harvest installation script.
If the ingres user does not already exist, ensure that all users have read and execute permission to the parent folders of the AllFusion Harvest installation script.
Run the installation again.
Novell SUSE LINUX Enterprise Server 8.2-libgcc 3.3-23.i586 rpm and libstdc++ 3.3-23.i586.rpm
Novell SUSE LINUX Enterprise Server 9.0 -libgcc 3.3.1-29.i586 rpm and libstdc++ 3.3.1-29.i586.rpm
Novell SUSE LINUX Enterprise Server 9.1-libgcc 3.3.3-41.i586 rpm and libstdc++ 3.3.3-41.i586.rpm
If the libgcc_s.so.* file is missing, install the libgcc-*.i386.rpm package
If the libstdc++.so.* file is missing, install the libstdc++-*.i386.rpm package
If the libstdc++-libc6.2-2.so.* file is missing, install the compat-libstdc++*.i386.rpm package
Open the Windows command prompt.
Change to the %HARVESTHOME%installPEC directory.
Enter the following command to run the PEC installation silently: launch /s
Adding the following lines in the Harweb configuration file, harweb.cfg:

user= username

password= password
where username and password are your user name and password for accessing your AllFusion Harvest database.
Using Sun Java System Web Server 6.1 SP4 on Solaris 9
Using Tomcat 5.0.25, 5.5.4, 5.5.7, or 5.5.9 on Solaris 10
On the computer running WebSphere Application Server, change to the WebSphere Application Server installation directory.
Change to the /bin subdirectory.
In the /bin directory, edit the wsadmin.sh file.
Locate the following statement:

"$JAVA_HOME/bin/java"
On the next line, add the following: -Xmx192m
The new statement should be:

"$JAVA_HOME/bin/java"

-Xmx192m
Save the file.
Install and use the Microsoft SQL Server 2000 JDBC driver.
Upgrade your database to Microsoft SQL Server 2005. If you select this option, you must re-run the database configuration utility and re-install Harweb.
Araxis Ltd. Merge v6.5 Professional Edition
Guiffy Software, Inc. Guiffy 6.4
WinMerge 2.1.6.0
Scooter Software Inc. Beyond Compare 2 2.2.7
SoftInterface, Inc. Diff Doc 3.08
On Windows and Linux, install the Harvest server and specify Ingres as the DBMS for your Harvest database; in this case, the MDB is installed automatically during the Harvest server installation.
On Windows, install the Harvest server and specify Microsoft SQL Server as the DBMS for your Harvest database; in this case, the MDB is installed automatically when you create the Harvest database.
When the script is run, the contents of the context object reflect the current context values in the Workbench.
The information in this section does not apply to Visual Basic scripts that are not run in the Workbench or Administrator application.
At the command prompt, enter the following command to change to the %HARVESTHOME%Forms directory:

cd %HARVESTHOME%Forms
Open the form database script file and add the following text at the end of the file:
```
GRANT SELECT ,  UPDATE ,  INSERT ,  DELETE on tablename TO harvest_group
GO
GRANT SELECT on tablename TO harvest_rep
GO 
```
tablename
Specifies the name of the database table used in the CREATE TABLE statement in this script file.
Determine the Windows operating system user name of either the Harvest database owner or the sysadmin. To perform the next steps successfully, you must establish a trusted connection using one of these user names.
After you determine either user name, record it for use in the next step.

6.2 Administrator Guide-Unicenter Software Delivery Integration

Important! Add the new Step 5 to the steps listed in How You Enable Unicenter Software Delivery Integration in the chapter "Configuring Harvest Communication" in the CA Software Change Manager Administrator Guide. For context, the introductory text and the existing Steps 1-4 are also listed here.

To enable or reconfigure Unicenter Software Delivery Integration, set the following parameters to configure the communication and the synchronization of data between Harvest and Unicenter Software Delivery.
6.3 Administrator, Installation, and Reference guides

This update applies to the following sections:
To determine the sysadmin user, check your SQL Server documentation for instructions.
To determine the Harvest database owner, do the following:
If you are using SQL Server 2005, start SQL Server Management Studio.
If you are using SQL Server is 2000, start Enterprise Manager.
In SQL Server Management Studio or Enterprise Manager, locate the database named mdb and click it to display its users.
Right-click the user named dbo and select Properties. The login name of the dbo user is the Harvest database owner.
Log in to your Windows computer using the user name of either the Harvest database owner or the sysadmin user, which you determined in the previous step.
At the command prompt, run the following command:

osql -E -d mdb -i sqlfile -o output.log
Note: This command adds the form table to the Harvest database, using the SQL Server osql utility and passing the form file as a parameter. If any user runs the command successfully once , you cannot run it again , because the form table cannot be added to the database more than once. Therefore, if you try to run the command again, you receive an error message.
Start the Harvest Administrator application and click the Forms tab.
Ensure that the new form type is listed in the form type list.
If the DBMS is not on the same host where the form was created, copy the SQL file to the DBMS host and add it, as explained in the previous steps.
Set the URL for the Unicenter Software Delivery server.
Set the logon credentials (user name and password) for accessing the Unicenter Software Delivery server from Harvest.
Set the logon credentials for accessing the Harvest remote agent running on the Unicenter Software Delivery server.
Set the synchronization interval between Harvest and the Unicenter Software Delivery Server.
Import the Deploy Release Model life cycle template by running himpenv, the Harvest import command line utility.

Note: The Deploy Release Model life cycle template is required to use Unicenter Software Delivery Integration; this life cycle template is not installed automatically, even if you install Unicenter Software Delivery Integration when you install the Harvest server.
Use the following syntax as a model:
```
himpenv -b broker -f DeployReleaseModel.har -usr harvest_username -pw harvest password
```
-b broker
Specifies the name of your Harvest broker.

-f DeployReleaseModel.har
Specifies the complete path name of the Deploy Release Model life cycle template. This file resides in the HARVESTHOME directory.

-usr harvest_username
Specifies the user name of a Harvest user with administrator rights.

-pw harvest password
Specifies the password for this administrative user.

For more details about using the himpenv command, see the CA Software Change Manager Reference Guide.
External Authentication Connection Options for OpenLDAP in the section How You Configure External Authentication in the chapter "Configuring Harvest Communication" in the CA Software Change Manager Administrator Guide
External Authentication Connection Options for OpenLDAP in the section hauthtst Command--Authentication Server API Test in the chapter "Command Line Utilities" in the CA Software Change Manager Reference Guide

The following sections in the CA Software Change Manager Installation Guide:

You can optionally specify multiple base distinguished names when searching for user names in the LDAP server. To account for this new capability, replace the existing description of the -ldapbasedn= base-distinguished-name parameter with the following:

-ldapbasedn=" name1 [; name2 [; name 3 ]…]"

Defines one or more base distinguished names (DN) used when searching in the LDAP server.

To specify one base distinguished name, use the format shown in the following example: -ldapbasedn="ou=america,dc=abccorp,dc=com"

To specify two base distinguished names, use the format shown in the following example:

-ldapbasedn="ou=america,dc=abccorp,dc=com;ou=europe,dc=abccorp,dc=com"

Important! When specifying multiple base distinguished names, separate them with a semicolon (;), as shown in the previous example.

Default: None

Limits: 255 characters

6.4 Administrator Guide and Harvest GUI Help

This update is for the CA Software Change Manager Administrator Guide , in the chapter "Defining Process Properties," in Notify Properties.

Add the following updates to the description of the Mail Utility field on the Notify tab of the Notify Properties dialog: The default value is mail.

Add the same update to the Notify Properties topic in the Harvest GUI help.

6.5 Reference Guide

For the new -nvf option for the hco command, add the following text to the section "hco Command - Check-out" in the chapter "Command Line Utilities" in the CA Software Change Manager Reference Guide.

-nvf (Optional.) Specifies how AllFusion Harvest handles "file not found" errors that occur when the hco command is running.

When you specify -nvf, if one or more items specified is missing or if no item matching the wildcard search criteria is found, then AllFusion Harvest aborts the check out, displays an error message, and returns error code 14.

When you do not specify -nvf, if one of the conditions occurs, then AllFusion Harvest continues the check out, displays a warning message, and returns a "successful" code.

6.6 Message Guide

Update the following messages in the CA Software Change Manager Message Guide. These messages, reasons, and actions replace the existing ones.

I0002056c: Notify program: %s1 has been successfully launched.

Reason: %s1 is the notify program.

Action: None. Informational only.

Note: This email may not reach one or more recipients for various reasons, for example: problems with the network or mail server of the sender, receiver, or both; invalid email addresses; and so forth.

W01020178: No user email addresses found for the notify process.

Reason: Cannot find the email addresses for the users or user groups for the notify process.

Action: Check the property of the users to ensure that their email addresses are specified. Also ensure that the user groups do contain users and do have "Use Access" access right to the project.

Add the following new message to Harvest Warning Messages in the CA Software Change Manager Message Guide :

W010a0074 Warning: No version found for filename or pattern: %s1.

Reason: A version that matches the filename or pattern specified at the hco command line check-out cannot be found.

Action: Correct the filename or pattern specified for hco if they are misspelled, or remove the filename or pattern from hco if there is no version that matches the filename or pattern.

6.7 Reference Guide, User Guide, and GUI Help for Administrator Application

Important! The method that the hco command utility uses to determine whether to replace read-only files at check-out time has changed in Harvest r7.1. This change may impact users of the hco command who previously relied on the related Administrator application setting to determine whether to replace read-only files at check out. Check your hco commands on the command line and in scripts to ensure that this change does not cause the commands to fail or produce unexpected results. If necessary, update your hco commands to re-produce the expected results. For details, see PR2792 in Known Issues.

7.0 Known Issues

This section lists the most prominent known issues for AllFusion Harvest r7.1 at publication time. For other known issues, see Customer Support at https://support.ca.com.

7.1 How to Find Known Issues and Fixes

To find known issues and fixes, use the Knowledge Base on Customer Support. Follow these steps:

7.2 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).

7.3 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 AllFusion Harvest Workbench GUI, you receive a login timeout error if both of the following conditions exist:

As a workaround, try 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 AllFusion 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.4 Broker Shutdown

The AllFusion Harvest broker options file (HBroker.arg) in the $HARVESTHOME directory includes several options for specifying how AllFusion Harvest server processes are started, run, and shut down.

The -killperiod= seconds option (default=300) in the HBroker.arg file defines the amount of time that temporary server processes can be idle before the AllFusion Harvest broker shuts them down. Temporary server processes are server processes started in addition to the server processes started by the -minserver setting. The -minserver setting specifies the minimum number of server processes to be started.

On Red Hat Enterprise Linux Advanced Server 3.0, regardless of the -killperiod value specified, temporary server processes above the -minserver setting are shut down if they are idle for 30 seconds.

As a workaround to prevent constant shutdown and startup cycles, set the -minserver value equal to the -maxserver value. The -maxserver option specifies maximum number of server processes that can be running at the same time. For more information about HBroker.arg and its options, see the CA Software Change Manager Administrator Guide.

7.5 Character Sets

PR3907: Extended ASCII characters are dropped or not displayed correctly in queries or AllFusion Harvest GUIs.

The operating system character set and the nls_lang or lang variables used on the AllFusion Harvest server and client computers must match the character set and nls_lang variables used in the AllFusion Harvest database. If the character sets differ between client shells and the database, some extended ASCII characters inserted and selected with queries do not display correctly or may be dropped.

In Ingres, extended ASCII characters are not supported in literal query strings. For other databases, consult the DBMS documentation on how to verify and change the character set and other language variables on the specific operating system.

7.6 Check In and Check Out

PR2792: The method that the hco command utility uses to determine whether to replace existing read-only files at check-out time has changed in Harvest r7.1. Previously, when you ran hco:

PR2912: Generally, two AllFusion Harvest users can share the same project files; 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 AllFusion Harvest client, you may receive error messages similar to the following, even if the files are actually checked in or checked out properly:

E0380003: Requested Message Key Not Found: : HSRV_I_CHECKIN

E0380003: Requested Message Key Not Found: : HAPI_I_EXECUTE_SUCCESS

E0380003: Requested Message Key Not Found: : HSRV_I_CHECKOUT
E0380003: 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.

PR2948: If the client path name on a check out is set to read-only, the checkout attempt fails and you receive a message similar to the following:

E03020028: File Agent error for item <drive><path>File A.txt: Permission denied or the file is being used by another process.

The error message does not specify that the path is read-only. To fix this problem, ensure that the user attempting the check out has write access to the client path name. If necessary, see your system administrator for assistance.

PR3763: This is a problem within Rational Rose when SourceSafe is used as a Source Control provider. After performing undo checkout on a checked out file, the decorator next to the file still shows it as being checked out (checkmark).

As a workaround, users can click View Browser twice, so that the decorators are refreshed.

PR3990: When using AllFusion Harvest and Ingres, you can check in files greater than 132 MB into the AllFusion Harvest database but cannot check them out. Therefore, if you are using AllFusion Harvest and Ingres, do not check in files greater than 132 MB into the AllFusion Harvest database if you will need to check them out later.

PR4232: The hco command line utility includes a new option, -nvf. This new option enables you to specify how AllFusion Harvest handles "file not found" errors that occur when the hco command is running. For details, see Documentation Changes.

PR4426: Windows has a limit of 240 or 244 characters for path names. On Windows systems, if you check out files from a view path which is longer than 240 characters, you will receive a file agent error. The file agent is unable to write the file because of the path name length limitation.

PR4468: This problem occurs in Rational Rose when you try to check out a reserved file (an already checked out file). No error message displays, and the Harvest Workbench is launched.

7.7 Command Line

PR2914: The project restore command line utility named hrt requires a remote file agent connection on the computer where the project was archived. For example, to restore a project to AllFusion Harvest from computer A, a remote file agent must be running on computer A. Use the following syntax for hrt:

  hrt -b <broker> -f <archive file> -m <computer> -musr <user> -mpw <password> 
    -user <harvest user> -pw <harvest pw>

For more information about the hrt command, including its options for restoring projects on remote computers, see the CA Software Change Manager Reference Guide.

Important! For important updates for the hco command line utility, see PR2792 and PR4232 in Check In and Check Out in the Known Issues, and also see Documentation Changes.

PR5653: The behavior of the -args option for the hexecp command has been changed. The -args option now accepts multiple arguments. Each argument may or may not contain spaces. For example:

-args "a 1" "a 2" "a3" a4

If an argument contains a space, it is passed to the user's process as one argument with quotation marks. For example, "a 1" is passed to the user's process as "a 1".

If an argument does not contain a space, it is passed to the user's process without quotation marks. For example, "a3" and a4 are passed to the user's process as a3 and a4.

This change forces scripts that have -args "a 1 2 3" to be modified to: -args a 1 2 3

so that four arguments can be passed to the user's process. If not "a 1 2 3" will be passed to the user's process as one argument.

7.8 Direct Connection Considerations

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

Note: The host name is a text string up to 24 characters consisting of the alphabet (A-Z), digits (0-9), or a hyphen (-). No distinction is made between upper and lower case. The first character must be an alpha character. The last character must not be a hyphen.

7.9 Forms

PR4633: If you are using Ingres on Linux, when you start the AllFusion Harvest broker, you may receive an error message in the HServer.log file similar to the following: ERROR: [CA][Ingres ODBC Driver]Ingres API failure probably to due to transaction already abnormally terminated SQLSTATE=S1000

To correct this problem, rename the

$ODBC_HOME/lib/libiiodbcdriver.1.so file to
$ODBC_HOME/lib/ xxx libiiodbcdriver.1.so.

Depending on how security is implemented in your environment, you may require root access to rename the file.

PR4655: If you are using Ingres or Microsoft SQL Server, when you delete a form using the Forms tab of the AllFusion Harvest Administrator application, an error message similar to the following displays: Formtype delete failed.

The message displays even though the form is actually deleted. You can verify that the form was deleted by refreshing and checking the existing forms available in the AllFusion Harvest Workbench.

After you receive the error message, you cannot recreate a form with the same name as the one you deleted. If you do not need to recreate a form with the same name, you can simply use a different name. If you do need to recreate a form the same name, then before recreating the form, you must manually delete the Ingres or Microsoft SQL Server database table that has the same name as the form. To do so, follow the steps for the DBMS you are using:

If you are using Ingres, follow these steps:

If you are using Microsoft SQL Server, follow these steps:

PR5692: When you attempt to add the form table to a Harvest database running on SQL Server, you may receive an error message similar to the following:

Create table permission denied in database 'mdb'

If you receive this message, see Administrator Guide--Form Tables in SQL Server in the Documentation Changes section in this readme and perform the steps listed in that section.

7.10 Graphical User Interface

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

PR2917: In the Administrator application, 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.

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:

PR4035: In the Administrator application, if you open the process list for any state and drag and drop any column before the Name column, the columns and rows may not be refreshed correctly. Instead, the characters in the first column and other columns may become unreadable.

PR4039: In the Administrator application, if you are using Ingres, when you load a repository, you may receive error messages similar to the following if you do not check the Compress option on the Load Repository dialog: E03020003: Database Error: [CA][Ingres ODBC Driver]String data, length
mismatch SQLSTATE=22026. E0306001b: ERROR: Load repository items failed.

As a workaround, check the Compress Option on the Load Repository dialog.

7.11 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, AllFusion 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, AllFusion 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.

PR3413: Harweb will not work inside of Eclipse 3.0 when Eclipse 3.0 is installed on a UNIX platform. The SWT browser is only ported on Windows (Internet Explorer 6 or above), Mac (Panther OS X.3 or above, Safari based), and Linux GTK and Linux Motif (both using Mozilla 1.4 GTK2 - or above 1).

PR4624: When using Harweb, you may encounter problems or failures when attempting to check in or check out large numbers of files--for example, on some systems, several thousand files. The number of files that you can check in and check out successfully depends on many factors, including hardware configuration, application server configuration, memory, database configuration, file sizes, and system load.

PR5358: When logging in to Harweb or using Harweb, you cannot use single (') or double (") quotation marks in Harvest user names.

PR5480: If you upgrade a Harweb installation that uses Websphere Application Server 5.x or 6.x, some Harweb files may not be deployed or some folders may not be created properly, even though those files and folders do exist in the upgraded Harweb.war folder that the Harweb upgrade wizard created. As a work-around to upgrade your version of Harweb, do the following:

PR5668: When you use Harweb with a supported Apache Tomcat 5.x servlet engine, non-English characters may display as corrupted. To fix this problem, add the following connector string in the tomcathome confserver.xml file: URIEncoding=" YourCharacterSet " useBodyEncodingForURI=" YourCharacterSet "

In that file, add the string in the following location:

…  <Connector port="8080" maxThreads="150" minSpareThreads="25" 
maxSpareThreads="75"                 enableLookups="false" redirectPort="8443" 
acceptCount="100" debug="0" connectionTimeout="20000" 
disableUploadTimeout="true" 
URIEncoding=" YourCharacterSet " useBodyEncodingForURI=" YourCharacterSet " />  
…

For YourCharacterSet , specify the same connector string entered for your language in the Harweb configuration file, harweb.cfg. For example, if you are using the Japanese2 character set, specify the following connector string: URIEncoding="Shift-JIS" useBodyEncodingForURI="Shift-JIS"

7.12 hco Command

Important! For important updates for the hco command line utility, see PR2792 and PR4232 in Check In and Check Out in the Known Issues, and also see Documentation Changes.

7.13 HSDK

PR5581: You can run the Hsdksample program on Red Hat Enterprise Linux Advanced Server 4.0; however, to rebuild the sample code, you must use Red Hat Enterprise Linux Advanced Server 3.0 or another Linux version that uses the libstdc++.so.5 library.

Similarly, you can run the Hsdksample program on Red Hat Enterprise Linux Enterprise Server 4.0; however, to rebuild the sample code, you must use Red Hat Enterprise Linux Enterprise Server 3.0 or another Linux version that uses the libstdc++.so.5 library.

7.14 Ingres

PR5678: If you have installed Harvest with an Ingres database on a double-byte language computer, you may experience problems creating users, creating packages, and performing other tasks. The double-byte languages that Harvest supports are Japanese, Korean, Simplified Chinese, and traditional Chinese. To fix this problem, download and install the applicable Ingres patch for double-byte languages from Customer Support at https://support.ca.com.

Important! See also the Forms section in the Known Issues for form-related issues that apply to Ingres!

7.15 Installation

Note: For additional installation-related information in this readme, see Installation Considerations and see CA Software Change Manager Installation Guide in Documentation Changes.

PR2927: The AllFusion 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 AllFusion Harvest server fails to start. To work around this problem, follow these steps:

PR4401: Due to a defect in Sun Java, the directory selection dialog is not working as expected. After selecting a directory file, it is repeated twice in the File location. For more information, see the Sun website, http://sun.com.

PR4700: When deploying Harweb on Sun Java System Web Server, update the internal library path names of the web server with the AllFusion Harvest libraries. To do so, follow these steps:

7.16 Illegal Characters

PR2932: If you rename a checked-in item to include illegal AllFusion 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 AllFusion Harvest file names:

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

PR3950: When creating an AllFusion Harvest repository, ensure that the repository name includes no forward or backward slashes; otherwise, the attempt fails with an error message like the following: E03020190 ERROR: The repository name shouldn't contain: or /.

PR4516: On Windows, if you are using international character codes for folder and file names, be aware that depending on the client locale and character sets enabled on the computer, file folders or their contents may not be visible from the Workbench GUI. AllFusion Harvest uses Multi-Byte Character Set (MBCS) strings to hold folder and file names, and not all Unicode character values are translatable into MBCS character sequences.

For example, when using the AllFusion Harvest Workbench on a Japanese-enabled client computer, characters not displayed in the Japanese Industrial Standard (JIS) selection on the Input Method Editor (IME) Pad Character list on the Language Bar should not be used for folder and filenames, if they are to be viewed from the AllFusion Harvest Workbench GUI.

7.17 Linux

PR2934: If you run an AllFusion Harvest component on Red Hat Enterprise Linux Advanced Server 3.0 or Enterprise Server 3.0 and you receive a runtime error stating that GLIBC is not defined, set the environment variable LD_ASSUME_KERNEL=2.4.1 before launching any AllFusion Harvest executable, including the broker, server, agent, and command line utilities.

For convenience, you can set this variable in the login profile for every user who will use AllFusion Harvest executables. If you use a script to start up your AllFusion Harvest server, or if you configure your system to start AllFusion Harvest automatically, you should also set this variable in the appropriate scripts, as follows: LD_ASSUME_KERNEL=2.4.1 export LD_ASSUME_KERNEL

If you are using the C shell, use the following command: setenv LD_ASSUME_KERNEL 2.4.1

7.18 Microsoft SQL Server

Important! See the Forms section in the Known Issues for form-related issues that apply to Microsoft SQL Server!

7.19 Oracle

PR3903: If you are using Oracle, you may not be able to check in and check out files larger than 1 GB, depending on how busy Oracle is and whether the system on which Oracle is installed provides enough RAM or virtual memory. If you experience problems attempting to check in and check out files larger than 1 GB, try increasing the system's RAM or virtual memory.

7.20 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, the user rabbit can create password RABBIT, Rabbit, raBBit, and so on. Validation fails only if the password is 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.21 TestDirector

PR4969: In TestDirector, if you create a new test, check out the test, and then attempt to delete the checked out test from the Harvest repository TestDirector, the attempt should fail. However, the attempt succeeds, and the checked out test is deleted. The same problem occurs in TestDirector if you delete folders that include checked out tests.

Note: In TestDirector, an error message is displayed, but the delete operation is successful.

PR5275: If you use the same view path for two or more TestDirector projects, you may encounter errors when checking in files. To resolve these errors, specify a unique view path for each TestDirector project.

7.22 Version Control Interface (VCI)

PR2938: When you are using AllFusion 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 workaround:

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

PR4365: This known issue does not apply if you are using one of the following:

If you are using any other combination of an AllFusion Harvest VCI version with VCI and a Visual Studio 2003 or 2005 version, then this known issue does apply. AllFusion Harvest r7.1 uses the same hp~ file format as Harvest 5.2.1 Patches 4 and 5. However, this format is newer than the hp~ file format used by AllFusion Harvest r7, AllFusion Harvest r5.2.1 GA, and AllFusion Harvest r5.2.1 Patches 1, 2, and 3.

The newer hp~ file format is not backward-compatible with the older format. The newer hp~ file format is migrated automatically when you install AllFusion Harvest r71 or upgrade to it. Therefore, if you install AllFusion Harvest r7.1, you cannot use the updated hp~ file with a version of AllFusion Harvest that is using the older hp~ format. After you install a Harvest release that converts the hp~ file to the newer format, you cannot convert the hp~ file back to the old format. Consider the following examples:

Example 1: You are using AllFusion Harvest r5.2.1 Patch 4 with VCI and you add a project P to AllFusion Harvest source code control; the hp~ file is in the newer format. If you convert back to an earlier version of AllFusion Harvest, such as r5.2.1 Patch 1 or if you upgrade to AllFusion Harvest r7 GA, the same project P no longer works correctly, because AllFusion Harvest is using an older hp~ file format than project P. To make project P work successfully again, upgrade to either AllFusion Harvest r7 Patch 1 or AllFusion Harvest r7.1.

Example 2: You are using AllFusion Harvest r7 with Patch 1 installed and you add a project P to AllFusion Harvest source code control; the hp~ file is in the newer format. If you convert back to an AllFusion Harvest r7 GA, the same project P no longer works correctly, because AllFusion Harvest is using an older hp~ file format than project P. To make project P work successfully again, upgrade to either AllFusion Harvest r7 Patch 1 or AllFusion Harvest r7.1.

7.23 z/OS Agent and ISPF Client

PR2190: When exiting the Harvest ISPF client, you may see the following message: BPXP018I THREAD 1252A28000000001, IN PROCESS 83886182, ENDED WITHOUT BEING
UNDUBBED WITH COMPLETION CODE 0013E000, AND REASON CODE 00000000.

This message is informational only and can be ignored; this message relates to mixed mode (MVS and Open Systems UNIX) process termination. If you do not want to see this message, modify your TSO profile with the following command: TSO PROFILE NOWTPMSG

PR3113: For RACF users only. If your attempt to log in to the z/OS agent fails because you have an invalid OMVS segment, you may receive the following misleading error messages: an "Inaccessible Initial directory" message followed by a "Wrong user name for agent" message. If you receive these messages and you believe that your OMVS segment, username, and password are valid, check the z/OS agent job log for RACF messages indicating why your login attempt failed.

PR3129: If the z/OS agent is restarted while Workbench users are connected, those users are no longer able to authenticate with the agent. Attempts to check in, check out, or list PDS contents fail, and no members are displayed in the selected data sets).

PR3130: The z/OS agent abends with a B37 or E37 error if you attempt to check out items to a full partitioned data set (PDS) or if you attempt to check out new items to a full directory. To prevent or address this problem, try one or more of the following:

If an ISPF client attempts to access an MVS data set, the list of members may not display, without any corresponding error message. This problem occurs if the data set is protected by a z/OS security product or if the attempt to read catalog information about the data set fails.

PR3132: For MVS PDS members, the file name filter is not supported on check in from the z/OS agent. To check in a subset of members from an MVS PDS or library, use the Find button to return all members, and then use Shift+Click, Ctrl+Click, or both to select the member(s) you require.

PR3133: AllFusion Harvest, by default, creates and uses temporary data sets in the HFS subsystem in the /tmp directory. These files may not always be cleaned up when the agent is shut down. Your standard housekeeping policies should include removing any leftover files in this directory. The AllFusion Harvest files may be identified as having the OWNER/GROUP set to match the userid associated with the z/OS agent job or task and will have names like nnnnnnnn .PO nnnnnn .SI nnnnnn .X nnnnnnn .Y nnnnnnn (where nnnnnn is numeric).

PR4036: The load repository function does not support MVS partitioned data sets (PDSs). If you attempt to use the load repository function for these data sets, error messages similar to the following are displayed: E0302003a: Unable to find files in < pds name > matching * . E0306001b: ERROR: Load repository items failed.

To add items from an MVS PDS to the AllFusion Harvest repository, use the check in process.

PR3140: The z/OS agent and ISPF client enable z/OS files to be checked in to an AllFusion Harvest repository as text files, performing ASCII-to-EBCDIC and record-to-stream conversion as needed. However, due to the limitations of code page conversion, not all permissible characters may be supported by this conversion. For information about code page conversion, see the IBM document z/OS V1R4.0 C/C++ Programming Guide (Document Number SC09-4765-03).

Therefore, we strongly recommend that you test to ensure that the code pages and character sets you use are compatible. If you have any doubt that the conversion does not support the source files you manage, we recommend setting the repository options to manage MVS and USS files in binary mode only.

PR4495: For users of BrightStor CA-PDSMAN PDS Library Management. Using the z/OS agent to check in approximately 7000 or more PDS members could possibly degrade the system and abort the agent. To fix the problem, apply the following solutions:

For BrightStor CA-PDSMAN PDS Library Management 7.4, apply the following:

For BrightStor CA-PDSMAN PDS Library Management 7.5, apply the following:

8.0 International Support

An internationalized product is an English product that runs correctly on local language versions of the required operating system and required third-party products, and supports local language data for input and output. Internationalized products also support the ability to specify local language conventions for date, time, currency and number formats.

A translated product (sometimes referred to as a localized product) is an internationalized product that includes local language support for the product's user interface, online help and other documentation, as well as local language default settings for date, time, currency, and number formats.

In addition to the English release of AllFusion Harvest, CA supports only those languages listed in the following table.

Language	Internationalized	Translated
Brazilian-Portuguese	Yes	No
Chinese (Simplified)	Yes	No
Chinese (Traditional)	Yes	No
French	Yes	No
German	Yes	No
Italian	Yes	No
Japanese	Yes	No
Korean	Yes	No
Spanish	Yes	No

Note: If you run AllFusion Harvest in a language environment not listed in the table, you may experience problems.

This English version of CA Software Change Manager Sample Reports has been certified to run on computers designed to use the English language.

9.0 Documentation

The file names for the PDF guides are as follows:

Guide Name	File Name
Administrator Guide	Harvest_Admin_ENU.pdf
COM SDK Reference Guide	Harvest_COMSDK_ENU.pdf
Getting Started	Harvest_GetStart_ENU.pdf
Installation Guide	Harvest_Install_ENU.pdf
Integration Tools User Guide	Harvest_IntTools_ENU.pdf
Reference Guide	Harvest_Ref_ENU.pdf
Release Summary	Harvest_RelSum_ENU.pdf
Sample Reports User Guide	Harvest_Reports_ENU.pdf
SDK Reference Guide	Harvest_SDKRef_ENU.pdf
Tutorial Guide	Harvest_Tutorial_ENU.pdf
User Guide	Harvest_User_ENU.pdf
Version Control Interface User Guide	Harvest_VCInterface_ENU.pdf
MDB Overview	MDBOverview_enu.pdf

To view PDF files, you must download and install the Adobe Reader from the Adobe website if it is not already installed on your computer.

For updated guides, see Customer Support at https://support.ca.com.

10.0 Contact Customer Support

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

The sections named LDAP Compliant Directory Configuration Windows in the chapters "Upgrading or Installing the Harvest Server on Windows" and "Upgrading or Installing the Harvest Agent on Windows"
The sections named LDAP Compliant Directory Configuration Parameters in the chapters "Upgrading or Installing the Harvest Server on UNIX and Linux" and "Upgrading or Installing the Harvest Agent on UNIX and Linux"
Log in to Customer Support.
Click Knowledge Base.
Select AllFusion Harvest product.
Enter keywords.
Select criteria for your search by checking for the following: Reported Problems, Published Solutions, FAQs, and Technical Documents.
Click Search.
The computer name of your AllFusion Harvest broker includes a dash (-)
The remote AllFusion Harvest agent is already connected to that broker
If you did specify the -r option to replace read-only files in your command syntax, hco replaced all existing read-only files.
This behavior remains the same for Harvest r7.1.
If you did not specify -r option to replace read-only files in your command syntax, hco automatically used the setting specified in the Replace Read Only Files check box in the Defaults tab of the Checkout Properties dialog of the Administrator application. Based on that Administrator setting, hco either replaced existing read-only files or left them as-is.
This behavior has changed. In Harvest r7.1, when you run hco at the command line or in a script, if you do not specify the -r option, the check out does not replace any existing read-only files, regardless of the Administrator application setting.
Important! This change may impact users of the hco command who previously relied on the Administrator application setting to determine whether to replace read-only files at check out. Check your hco commands on the command line and in scripts to ensure that this change does not cause the commands to fail or produce unexpected results. If necessary, update your hco commands to re-produce the expected results.
Client to Server (for example: check out to local file system): Client host must be able to resolve the Server's host name to an IP address.
Client to Remote Agent (for example: log in to Remote Agent): Client host must be able to resolve the Remote Agent's host name to an IP address.
Remote Agent to Server (for example: check out to Remote Agent): Remote Agent host must be able to resolve the Server's host name to an IP address.
Log in to the computer on which Ingres is installed.
Use one of the following methods. In both drop commands, tablename specifies the name of the database table that you want to drop.
On the command line, enter the following command:
```
sql -umdbadmin mdb 
```
The SQL Terminal Monitor utility starts. At the SQL Terminal Monitor prompt, enter the following command to drop the table:
```
drop table tablenameg
```
Enter q to exit the SQL Terminal Monitor utility.
Create an SQL script named droptable.sql with the following content:
```
drop table tablename
pg
```
On the command line, enter the following command:
```
sql -umdbadmin mdb 
```
Log in to the computer on which SQL Server is installed.
Determine the Windows operating system user name of either the Harvest database owner or the sysadmin user. To perform the next steps successfully, you must establish a trusted connection using one of these user names.
After you determine either user name, record it for use in the next step.
To determine the sysadmin user, check your SQL Server documentation for instructions.
To determine the Harvest database owner, do the following:

If you are using SQL Server 2005, start SQL Server Management Studio.

If you are using SQL Server is 2000, start Enterprise Manager.

In SQL Server Management Studio or Enterprise Manager, locate the database named mdb and click it to display its users.

Right-click the user named dbo and select Properties. The login name of the dbo user is the Harvest database owner.
Log in to your Windows computer using the user name of either the Harvest database owner or the sysadmin user, which you determined in the previous step.
At the command prompt, enter the following command:
```
osql -E -d mdb
 
 -E 
```
Specifies Windows authentication.
```
-d mdb 
```
Specifies the AllFusion Harvest database named mdb.
The Microsoft SQL Server osql utility starts. At the prompt, enter the following command to drop the table:
```
drop table
 
 go tablename 
```
To exit the Microsoft SQL Server osql utility, enter quit .
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.
When you browse files, you can change the Client View Path if Use Context View Path is not checked or if Use Client View Path is checked.
Use the Websphere Administration Console to uninstall your existing version of Harweb.
Stop the Websphere application server.
Delete the Harweb.ear folder from the installedApps directory.
Restart Websphere application server.
Use the Harweb installation wizard to install the new version of Harweb as a first-time installation. For instructions, see the CA Software Change Manager Installation Guide.
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.
Restart the AllFusion Harvest broker and RTserver if they are already running.
Log in to the Admin console of Sun Java System Web Server.
Select Manage WebServer.
Select Java.
Select JVM Path Settings.
Add the following path names to Native Lib Path Prefix. These names are the default path names. If you are using different path names, enter your path names instead: /opt/CA/CAcrypto: /opt/CA/harvest/lib: /opt/CA/pec/lib/i86_linux24
quotation mark (")
forward slash (/), backward slash (), or vertical separator (|)
colon (:)
asterisk (*)
question mark (?)
carets (< >)
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 AllFusion 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.
AllFusion Harvest r7 Patch 1 VCI with Visual Studio 2003
AllFusion Harvest r7 Patch 2 VCI with Visual Studio 2005
Use partitioned data set/extended (PDS/E) format instead of PDS format. At publication time, IBM recommends PDS/E format.
Compress your data sets frequently.
Carefully monitor directory usage, extents, and free space in your data sets. Whenever necessary, create new data sets, or reorganize existing ones, to suit your needs.
Use a utility such as BrightStor CA-PDSMAN PDS Library Management. This CA solution addresses many common library issues and which can dynamically reallocate the unused or "dead" space in a PDS. For more details about this solution, see Customer Support at https://support.ca.com.
Solution: PM74609
Apar: 391 QO59126
Description: LSQA usage may creep in some situations
Solution: PM75044
Apar: 391 38 QO63314
Description: Possible SD78-04 after applying PM75009
Solution: PM75009
Apar: 10 QO59100
Description: LSQA usage may creep in some situations
Solution: PM75044
Apar: 38 QO63314
Description: Possible SD78-04 after applying PM75009