AllFusion Harweb 3.1 SP1 GA Release - CA Technologies
{{search ? 'Close':'Search'}}
****************************************************************

AllFusion Harweb 3.1 SP1 GA Release

****************************************************************


****************************************************************
Contents
****************************************************************

1.0 Welcome

2.0 Installation Considerations

3.0 Patch installation
3.1 UNIX Installation
3.2 WINDOWS Installation

4.0 Problems corrected
4.1 Problems fixed in 3.1 GA Release
4.2 Problems fixed in 3.1 SP1 GA Release

5.0 Additional information on problems corrected

6.0 Contacting Technical Support


****************************************************************
1.0 Welcome
****************************************************************

This Readme file contains installation considerations as
well as patch installation instructions, problems
corrected, known issues, and contacting Technical Support.


****************************************************************
2.0 Installation Considerations
****************************************************************

* In addition to the HARWEB Service Pack, Harweb 3.1 SP1 also
requires the installation of the HARVEST 5.1.1 SP1.

Please refer to the HARVEST 5.1.1 SP1 patch README.TXT for
installation instructions.

The minimum Harvest 5.1.1 SP1 patch level required for this
HARWEB patch is: HARVEST 5.1.1 SP1 GA Release.

* Please apply this PATCH/FIX to the corresponding Harweb
Server installation.

* The PATCH files are cumulative; in other words, applying
the latest PATCH file provides all fixes.

For example: HARWEB31SP1PATCH005 contains all fixes from
HARWEB31SP1PATCH001 to HARWEB31SP1PATCH005.

* To apply a patch/fix go to the APPLY PATCH/FIX section.

* The difference between HARWEB31SP1PATCH005 and HARWEB31SP1PATCH005FIX,
is that the first refers to a publicly available PATCH (patch 5),
and the second refers to a set of intermediate FIXES available
after the PATCH (patch 5).

* Intermediate FIXES are usually included in the next publicly
available PATCH.


****************************************************************
3.0 Patch installation
****************************************************************

Note: BACKUP the original files. This process overwrites the
original files.

Note: Edit "<webappdir>HarwebWEB-INFharweb.cfg" and
append/modify the following line:
CharacterSet = <yourCharacterSet>

This character-set is used to determine how to translate
the bytes within the web-pages into characters on the screen.
It is not related to the database character-set; it depends
on the Language and Web Browser utilized.

For example (using Microsoft Internet Explorer as the Web Browser):
- if the language is English, you can set: CharacterSet=iso-8859-1.
- if the language is Chinese Simplified. You can set: CharacterSet=gb2312 .

Please refer to the web-links below for additional information
on web-browser/language/character-sets:
- http://www.w3.org/International/O-charset-lang.html
- http://www.w3.org/International/O-charset-list.html

________________________________________________________________
3.1 UNIX installation
________________________________________________________________

To apply the PATCH/FIX, perform the following steps:

1. Logon to the Operating System using the UNIX Harweb account.
2. Close all Harweb Client Applications.
3. Shutdown the Harweb Server components.
4. Change the current directory to the HarWeb home directory
(<webappdir>Harweb). This directory should contain the
directories <webappdir>HarwebHarweb
and <webappdir>HarwebWEB-INF.
5. Backup the following directories: <webappdir>HarwebHarweb
and <webappdir>HarwebWEB-INF.
For example (within Harweb home directory):
"tar cvf HARWEB_BKP.tar Harweb WEB-INF".
6. Copy the "<patch>.tar.gz" file to the HarWeb home directory
(<webappdir>Harweb).
7. Delete the following files (if they exist) from the Harweb
home directory: PATCH.log, ApplyPATCH.sh, README.TXT
8. Decompress the PATCH file using: "gzip -d <patch>.tar.gz".
9. Un-tar the PATCH file into the Harweb home directory
using: "tar xvfo <patch>.tar".
10. Execute "ApplyPATCH.sh"
11. Start the Harweb Server components.

________________________________________________________________
3.2 WINDOWS Installation
________________________________________________________________

To apply the PATCH/FIX, perform the following steps:

1. Logon to the Operating System using the Local Administrator
account.
2. Close all Harweb Client Applications.
3. Shutdown the Harweb Server components.
4. Backup the following directories: <webappdir>HarwebHarweb
and <webappdir>HarwebWEB-INF.
5. Decompress the "<patch>.zip" file to the Harweb home directory
(<webappdir>HarWeb). This will overwrite all files in
<webappdir>HarwebHarweb and <webappdir>HarwebWEB-INF.
6. Start the Harweb Server components.


****************************************************************
4.0 Problems corrected
****************************************************************

Note: An asterisk (*) indicates to refer to the section
"5.0 Additional information on problems corrected"

________________________________________________________________
4.1 Problems fixed in 3.1 GA Release
________________________________________________________________

1004 - SELECT SQL STATEMENT IS ONLY ALLOWED IN WEBSQL
1264 - HARWEB AND WEBSPHERE INTEGRATION

________________________________________________________________
4.2 Problems fixed in 3.1 SP1 GA Release
________________________________________________________________

925 - HARWEB CONTAINS HARVEST DATABASE USER/PASSWORD IN CLEAR TEXT
(*) 930 - CHECKOUT FOR RESERVE FOLLOWED BY CHECKIN FOR RELEASE TRIES TO ACCESS FILES VIA A CLIENT-PATH
943 - VIEW NAVIGATE PAGE DOES NOT DISPLAY PROCESS LIST WITH THE RIGHT ACCESS
945 - CANNOT UPDATE CHECKBOX IN HARWEB FORM PROPERLY
994 - GET ERROR 500 WHEN CLICKING HARVEST LOGIN THROUGH HARWEB IIS/TOMCAT
1051 - FIND VERSION RETURNS ALL VERSIONS
1074 - HARWEB IS NOT ABLE TO UPDATE VIEWS FROM ADMIN
1104 - USERS WITH NO UPDATEPACKAGEACCESS ARE ABLE TO MODIFY THE FORM
1111 - MISSPELLING OF LATEST IN FIND VERSION DROP DOWN LIST
1126 - HARWEB 3.1 C90 INTERNATIONALIZATION
1133 - REPOSITORY FILE EXTENSIONS NOT CONVERTED TO UPPERCASE
1171 - THE VALUE OF THE RADIO BUTTON CANNOT BE RETRIEVED IN HARWEB FORM
1213 - UPGRADED HARWEB FOR NEWER J2EE
1235 - CANNOT VIEW VERSION WHEN THERE IS ALREADY A SAME NAME FILE IN THE TEMP DIRECTORY
1263 - NO DIRECTORY CHOOSER BUTTON FOR LOAD REPOSITORY
1269 - VALUE OF CHECKBOX "DELETE FILES AFTER CHECKIN" IS NOT DISPLAYED CORRECTLY
1300 - RUNTIME ERROR OCCURS WHEN NO ITEM OR ITEM PATH IS SELECTED
1306 - CANNOT CREATE PACKAGE WITH SPACES IN THE MACRO NAME
1313 - DEFAULT OPTIONS OF A CHECKIN PROCESS NOT SAVED AND RETRIEVED CORRECTLY
1353 - UPDATING USER ACCESS IN PROJECT DOES NOT DISPLAY MESSAGE THAT PROPERTIES HAVE CHANGED
1415 - REMOVE NON-PRINTABLE/CONTROL CHARACTERS IN CODE
(*) 1420 - MISMATCH IN THE PATH OPTIONS BETWEEN HARVEST CLIENT AND HARWEB
(*) 1433 - IN HARWEB, REMOVING A FORM ASSOCIATION FROM A PACKAGE DOES NOT DELETE THE FORM
(*) 1455 - ORDER OF ITEM FILTER OPTIONS DIFFERENT BETWEEN HARVEST ADMIN AND HARWEB
1490 - CORRECT DEFAULT MODE OPTION FOR CHECKIN IS NOT DISPLAYED
1702 - FORM ATTACHMENT DOES NOT WORK WITH NETSCAPE 7.0

****************************************************************
5.0 Additional information on problems corrected
****************************************************************

925 - HARWEB CONTAINS HARVEST DATABASE USER/PASSWORD IN CLEAR TEXT

If the harweb.cfg file does not contain Harvest database user/password information,
then HarWeb will utilize the encrypted information within hsvr.dfo.

If the harweb.cfg file contains Harvest database user/password information,
then HarWeb will utilize the database user/password within harweb.cfg.

NOTE: If Harvest Server is not installed on the same machine as HarWeb,
then the "hsvr.dfo" file needs to be generated onto the HARVESTHOME directory
on the HarWeb machine using the "svrenc" utility.

930 - CHECKOUT FOR RESERVE FOLLOWED BY CHECKIN FOR RELEASE TRIES TO ACCESS FILES VIA A CLIENT-PATH

Checkout for Reserve does not require a client-path.

1420 - MISMATCH IN THE PATH OPTIONS BETWEEN HARVEST CLIENT AND HARWEB

The following Harweb default path options have been changed:

FROM: Preserve View Path Structure
Preserve and Create Directory Structure
All Files to the Same Client Directory

TO: Preserve Directory Structure
Preserve and Create Path Structure
All Files to the Same View Path

1433 - IN HARWEB, REMOVING A FORM ASSOCIATION FROM A PACKAGE DOES NOT DELETE THE FORM

- HUP command-line utility has been expanded; a new switch -del has been added.
When removing package/form associations, via the -rf <form name> or -rfo <form object id> switches,
adding the -del switch will also delete the form if it is not associated with any other package.

- HarWeb has also been updated when removing package/form associations.
The system now prompts for confirmation to delete the form if it is not associated with any other package.

1455 - ORDER OF ITEM FILTER OPTIONS DIFFERENT BETWEEN HARVEST ADMIN AND HARWEB

The following Harweb item filter options have been changed:

FROM: Existing Items Only
New Items Only
New or Existing Items

TO: New Items Only
Existing Items Only
New or Existing Items


****************************************************************
6.0 Contacting Technical Support
****************************************************************

See https://support.ca.com for the latest product information.
For further technical assistance with CA Software
Change Manager, contact Technical Support at 1-800-833-7528
Hours 0800-1800 CST

Operating System

File Size

MS WINDOWS 1.3 MB
UNIX 936 KB

Chat with CA

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

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

All Fields Required

connecting

We're matching your request.

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

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

    View Profile


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

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

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

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


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

    Take Our Survey >

    Rate Your Chat Experience.

    {{chat.statusMsg}}

agent is typing