Change Download Preference

Current Preference
Change Preference to:

CA Software Change Manager Plug-in for Eclipse Readme

1.0 Welcome

2.0 Platform Support
2.1 Windows
2.2 UNIX
2.3 Linux

3.0 System Requirements
3.1 Eclipse 3.0
3.2 Root Access Permission on UNIX and Linux

4.0 Installation Considerations
4.1 Eclipse SDK 3.0
4.2 Installing CA Software Plug-in for Eclipse on Windows
4.3 Installing CA Software Plug-in for Eclipse on UNIX, Linux (RedHat AS 3.0), HP, AIX, and Solaris

5.0 How to Find Known Issues and Fixes

6.0 Known Issues

7.0 Fixed Issues

8.0 Documentation

9.0 Contacting Customer Support


1.0 Welcome

Welcome to the readme for the AllFusion Harvest Change Manager Plug-in for Eclipse (hereafter called CA Software Plug-in for Eclipse) r6.0. This readme contains important information you need to know before installing or working with the CA Software Plug-in for Eclipse, formerly known as WebSphere Studio Integration. This file contains system requirements, known issues, technical support contact information, and acknowledgements. For information about other Harvest components on Windows, UNIX, and Linux, see the Harvest r5.2.1 Patch 3 CA Software Change Manager Readme on our web site,

2.0 Platform Support

This section lists the platforms supported by the CA Software Plug-in for Eclipse. Computer Associates supports these platforms for the duration of their life cycle (as determined by their manufacturer) or until Computer Associates announces that we are dropping support. For the latest information about supported platforms, see our web site,

2.1 Windows

The CA Software Plug-in for Eclipse is supported for Windows XP, Windows 2003, and Windows 2000.

2.2 UNIX

The CA Software Plug-in for Eclipse is supported on HP-UX, AIX, and Solaris.

2.3 Linux

CA Software Plug-in for Eclipse on Linux is only supported on Red Hat Linux AS 3.0.

3.0 System Requirements

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

3.1 Eclipse 3.0

Eclipse 3.0 must be separately installed on the supported platforms.

3.2 Root Access Permission on UNIX and Linux

If Eclipse 3.0 is installed in a common area to allow usage by multiple users or if Harvest is installed in a common area, then it will be necessary to run the install script for this enhancement with root access permission.

4.0 Installation Considerations

This section contains instructions for installing the CA Software Plug-in for Eclipse.

Before installing these enhancements, you must:

  1. Install Harvest 5.2.1 on each computer in your Harvest system, according to the instructions in the CA Software Change Manager Install Guide.

  2. Install Harvest 5.2.1 Patch 3 on each computer in your Harvest system, according to the instructions in the Harvest 5.2.1 Patch 3 CA Software Change Manager readme.

  3. Install Eclipse 3.0 on each computer in your Harvest system.

  4. Install Apache Tomcat Webserver 4.1.31 or 5.0.28 on each computer in your Harvest system.

  5. Launch Harweb externally from Eclipse 3.0 using Mozilla 1.4 to 1.7.

Note: Before proceeding, ensure that you download and have available the latest Harvest 5.2.1 Patch 3, especially the AllFusion Harvest Change Manager Install Guide and readme mentioned above, from

4.1 Eclipse SDK 3.0

Eclipse SDK 3.0 must be downloaded from and installed on the target systems prior to installing this enhancement.

Note: The SDK version of Eclipse 3.0 (for example, eclipse-SDK-3.x-...) MUST be downloaded and used, rather than the platform version (for example, eclipse-platform-3.x...). For example, HP-UX would need

The Eclipse SDK 3.0 includes the Eclipse Platform, Java development tools, and Plug-in Development Environment, including source and both user and programmer documentation. Eclipse does not include a Java runtime environment (JRE). You will need a 1.4.1 level or higher Java runtime or Java development kit (JDK) installed on your machine in order to run Eclipse.

4.2 Installing CA Software Plug-in for Eclipse on Windows

  1. Verify that Harvest Client 5.2.1 Patch 3 is installed by selecting Help, About from the Harvest Client main menu.

  2. Verify that Eclipse 3.0 is installed by selecting Help, About Eclipse Platform from the Eclipse main menu.

  3. Exit Eclipse 3.0 and Harvest applications.

  4. Launch the CA Software Plug-in for Eclipse install by double-clicking on the msi file or by entering msiexec from the command line. If Harvest 5.2.1 client and Patch 3 are not detected on the target system, the install will notify the user and abort.

  5. On the License Agreement dialog, read the terms and accept or decline. To continue installing, select Accept and click Next.

  6. On the Welcome dialog, click Next to continue.

  7. On the Eclipse Folder dialog, perform one of the following:

    After specifying the Eclipse folder, click Next to continue. The path for the Eclipse folder is validated. If the path specified is not valid, a message will notify you and the install will not continue.

  8. Click Search to automatically search for Eclipse products on the target system. If more than one Eclipse product is found on the target system, a dialog will display the search results. Select the Eclipse product from the list and click OK to continue.

  9. Click Change to manually change the directory.

  10. On the Ready to Install the Program dialog, click Install to begin the installation.

  11. The next screen displays a completion message. Click Finish to complete the install.

For more information about the admin install, silent install, and network install, please consult the CA Software Change Manager Install Guide or access the website to obtain help on the msiexec command line option.

Note: If any version prior to Eclipse 3.0 had been used with Harvest, this previous version of Eclipse will no longer be usable with Harvest after the installation of the Plug-in for Eclipse 3.0.

4.3 Installing CA Software Plug-in for Eclipse on UNIX, Linux (RedHat AS 3.0), HP, AIX, and Solaris

The enhancements are supplied in the following files:



Note: The same file name is used for each platform.

To install the enhancements, follow these steps:

  1. Ensure that the umask is set to 022.

  2. Log on to the machine using your UNIX Harvest account.

  3. If root access is required, then execute the "su" command and enter your root password.

  4. Close all Harvest client applications.

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

  6. Copy the HAR521PATCH003ECLIPSE.tar and files to your home directory.

  7. Change to the CA Software Plug-in for Eclipse installation directory.

  8. Enter the following command to decompress the file into your CA Software Plug-in for Eclipse installation directory, where XXX represents the path to your home directory:
    unzip /XXX/
  9. Change to the Harvest installation directory.

  10. Enter the following command to un-tar the file into your Harvest installation directory, where XXX represents the path to your home directory:
    tar xvfo /XXX/HAR521PATCH003ECLIPSE.tar
    Note: The following steps assume the use of a Bourne-compatible shell, such as "bash" or "ksh".

  11. Set PATH to include the current directory.
    PATH=.:$PATH export PATH
  12. Set Environment variables HARVESTHOME, ECLIPSE_HOME, RTHOME, and JAVA_HOME
     HARVESTHOME=<location of HARVEST 5.2.1> export HARVESTHOME ECLIPSE_HOME=<location of ECLIPSE> export ECLIPSE_HOME RTHOME=<location of PEC> export RTHOME JAVA_HOME=<location of Java> export JAVA_HOME 
  13. Before starting Eclipse it will be necessary to source the Harvest setup script, using a dot command.

    Notice the dot "." at the beginning of the next line:
  14. Eclipse may now be started.

5.0 How to Find Known Issues and Fixes

You can find Known Issues and Fixes by going through SupportConnect and the Knowledge Base.

  1. Login to SupportConnect.

  2. Click Knowledge Base.

  3. Select CA Software product.

  4. Enter keywords.

  5. Select criteria for your search by clicking on a checkmark box for the following:

    Reported Problems
    Published Solutions
    Technical Documents

  6. Click Search.

6.0 Known Issues

This section lists the most prominent known issues for Harvest r5.2.1 at publication time. For other known issues, see Computer Associates Customer Support at

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

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

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

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

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

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

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

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

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

  2. Synchronize with Harvest in WSAD Integration.

PR2944: While working in a project, if you rename an item and then attempt to rename it back to its old name, you receive an error message similar to the following:

 Cannot rename item; new name already exists. 

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

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

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

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

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

PR2949: If you are using Harweb hosted in IBM WebSphere Studio and you require Tomcat, you must use Tomcat 4.1.30 or 5.0.28. For details, see Installation Considerations earlier in this readme.

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

PR2951: This issue applies if you perform the following steps while using WSAD 5.1.1 and Eclipse 3.0 with Harvest r5.2.1:

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

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

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

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

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

PR2953: If you share a project, un-share it, immediately share it again, and then attempt to use the Move and Delete functions for the files in that project, the attempt fails, and Harvest displays an error message similar to the following:

 Problems occurred moving the selected resources:  Resource is out of sync with the file system... 

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

PR3365: The Standard Widget Toolkit (SWT) Browser widget that is used to display the embedded Harweb is not supported in Eclipse 3.0 for the UNIX platform. The SWT Browser widget is only ported in Windows, Linux, and Mac. On all variations of UNIX, the SWT widget is not ported and Harweb should be launched externally using Netscape/Mozilla.

The following platforms are supported by the SWT Browser:

  • Windows (Internet Explorer 5 or above)

  • Mac (Panther OS X.3 or above. Safari based)

  • Photon

  • Linux GTK and Linux Motif (both using Mozilla 1.4 GTK2 - or above). The Linux distributions that meet the Mozilla requirements for using the SWT Browser widget are RedHat Enterprise Linux 3 and SuSE 9.

PR3604: Copy/Paste of items from the File Manager to the Eclipse workspace does not work on HP, Solaris, and AIX due to a bug in Eclipse. Please refer to for more details. Copy/paste of items works fine on Windows and Linux.

PR3497: On Windows, if you have a checkout process selected in the Context dialog in Eclipse that has both update and concurrent enabled, and then you select refactor, rename on a file that is checked in, Eclipse displays the Refactor dialog. When the Harvest Eclipse plug-in then tries to perform the checkout options (concurrent or update), native Eclipse produces an exception and the refactor operation fails. The workaround is to perform a refresh of the project or file before the refactor rename operation.

PR3449: On Unix, Eclipse crashes when selecting File, Exit. This crash has been observed after the following series of actions: 1) adding a project to the workspace, 2) checking out a file for update, 3) making changes to the file, 4) checking in the file, and 5) then selecting File, Exit. An exception with the following message is displayed:

 An unexpected exception has been detected in the native code outside the VM. Unexpected signal :11 occurred at PC=0xFF232dFC 

This is a known Eclipse bug – Bugzilla ID 50145. It has been noted that native Eclipse 3.0 exhibits similar behavior on the Unix platforms. Please refer to for more details. The workaround is to use the 'X' icon to close. You may, however, lose your preferences when using the 'X' icon.

13657485: During a refactor, rename of a file that is currently checked in, the following error message is received:

 File '*******' has been modified since the beginning of the operation. 

There are two related known Eclipse bugs - Bugzilla ID 17611 and 74404. Please refer to and for more details. The workaround is to already have the file checked out before the refactor operation is started or click the Back button and try the refactor again (at that time the file is now checked out).

13686263: On Solaris and AIX, it is not possible to edit a read-only (checked-in) file while in offline mode. The "Modify read only?" dialog is displayed, but after clicking Yes, the file remains in Read Only mode and editing is not allowed in the editor. This is a known Eclipse bug-Bugzilla ID 32396. Please refer to for more details. The workaround is to manually add write permission to the file outside of Eclipse using the "chmod" shell command.

PR3343: When you attempt to change the harvest user within the same eclipse workspace, you will incorrectly receive the change password dialog. After you discard a harvest connection and create a new harvest connection with another harvest username, and then attempt to open a project, you will receive a change password dialog. You should not receive the change password dialog here. The workaround is to enter the password for the new harvest user in the change password dialog, then you can successfully open the project.

7.0 Fixed Issues

PR 3245: When using the Production Model lifecycle, Eclipse allowed you to check-in a new Trunk version into the Development state ignoring the check-in item filter option "existing items only." Eclipse always uses the filter option "new or existing items." This problem has been fixed to validate the filter option set for the check-in process. If there is no filter option selected, then the following error message is displayed:

 There is no item filter option set for the check in process. 

8.0 Documentation

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

The DIDs and file names for the Harvest guides are:

Guide Name DID File Name
Plug-in for Eclipse E00121-1E E001211E.PDF
Readme E00122-1E E001221E.html

9.0 Contacting Customer Support

For technical assistance with this product, contact Computer Associates Customer Support at for a complete list of locations and telephone numbers. Customer support is available 24 hours a day, 7 days a week.


CA Software Change Manager Plug-in for Eclipse 3.0 is available in the following downloads:

  • Eclipse Plug-in: Plug-in for Windows, UNIX and RedHat Linux.

  • Eclipse Harvest Setup Companion: This download contains the required Harvest 5.2.1 P3 setup scripts and supporting files to be installed on UNIX and RedHat Linux. Download the appropriate package for your desired platforms. The Windows Eclipse Plug-in download includes the Eclipse Harvest Setup Companion material.
Product Operating System - File Size
Documentation Readme(HTML) - 25.8 KB Readme(TEXT) - 22.0 KB User Guide(PDF) - 1.3 MB
Eclipse Plug-in Windows - 3.3 MB Solaris - 831 KB AIX - 831 KB HP-UX - 831 KB RedHat Linux - 831 KB
Eclipse Harvest Setup Companion Not Applicable Solaris - 3.0 MB AIX - 11.7 MB HP-UX - 4.1 MB RedHat Linux - 1.5 MB