Title: CCC/Harvest Release 5.01 Release Notes
Date: March 2001
The 5.0 release of CCC/Harvest provides powerful process-oriented software change control and management solutions for enterprise platforms.
CCC/Harvest 5.0 provides users with the following significant new features:
- New implementation architecture to free dependency from the Visix Galaxy programming environment.
- An intuitive way of executing day-to-day CM tasks using simple point, right-click and drag-and-drop methods.
- An advanced cross-platform communication service that connects NT, UNIX and MVS systems. This service provides a solid foundation for users to manage distributed CCC/Harvest client/server processes effectively. It also addresses the needs for porting client/server applications to mainframe environments.
- A new implementation that refines process, version, change package, and configuration management and data integrity, as well as enabling internationalization.
- A new agent technology that supports remote file check in/out between local workstations and remote UNIX machines or MVS on mainframe environments.
- Adopt ODBC implementation to access database system. Although only Oracle 8 database systems are currently supported, other database systems may be supported in the future.
- Establishes the C++ API, COM interface, Jasmine II foundations and new metadata model to address future integration needs including customization, Web-based operations, Unicenter TNG, Endevor, Software Deployment, Advanced Help Desk, project management and other CA tools.
New Features and Enhancements Summary
SCM Process Administration
- The object name "environment" is replaced with "project" to improve the usability of project-based SCM and facilitate future integration with other project-based tools.
- The copy or duplicate environment function is replaced with a new project template concept for the process of setting up a project lifecycle. In addition, users are able to copy a state and a state process between projects or project templates; this can greatly improve the usage of a UDP that is reused in multiple project lifecycles.
- The configuration of a project baseline is enhanced with greater flexibility. Users can configure baseline codes from one or many snapshot version lists or subsets of version lists.
- The project user list can now be integrated with user groups. Users can create user groups to be used in the project. This replaces the current CCC/Harvest environment user list.
- Archive and restore functions for a project is provided.
Change Package Management
- An extensive search function is available in the tool bar for locating change packages (for example, display a list of packages that are assigned to me or pending my approval). A right-click on the search results in the list box opens a shortcut menu with available package related processes such as promote, demote, or approval.
- A new package assignment attribute, "Assign to" is added to the change package object. This field displays the package assignee. Users can change the assignment by using the Package Properties dialog to select a user from a list of all defined CCC/Harvest users. This is the vehicle to get the individual’s TO DO List.
- A unique package name/number generation mechanism simplifies package creation.
- Whenever a package is approved, no change is allowed to related to the approved package until the package is moved to the different state.
- Detailed package approval information will be visible in the property of package
- GUI is properly refreshed after operating package/package group objects.
- A new package binding feature effectively manages change package dependencies.
- The bind attribute is introduced in the package group object. A user who is not a CCC/Harvest administrator can create a package group in the CCC/Harvest workbench interface and enforce the bind package feature to a package group. Through the Package Group Properties dialog, the user can add the related packages. The bind packages option enforces the following restrictions to packages belonging to a package group:
- A package can belong to only one bound package group.
- If a package is part of a bound package group and if Enforce Bind is enabled on the Demote or Promote Properties dialog, all packages in the group must be demoted or promoted together.
- To demote or promote individual packages that belong to a bound package group, the user must first unbind the package.
- Package operations (approve, promote, demote) can be performed on multiple packages or package group levels.
- A package list refresh button has been added to the Workbench toolbar for Harvest 5.01.
- A form must now be associated with at least one package because a form is considered a related attribute to a package.
- Galaxy-based forms are replaced with HTML-based forms.
- Using the new Form Creation Wizard users can create custom forms. To create a custom form, the user adds the form field to a tab page in the form construction tool. It also supports database combo control to allow dynamic selection list from database query.
- Forms can be concurrently updated without locking the individual form record.
- The form search function can now be used to select forms according to their association with packages. After locating packages, a right-click on the search results in the list box opens a shortcut menu with print, save, view and available processes options including promote, demote, approval, check-in.
- Supports form field validation
View and Version Management
- Users can execute processes from the Find Version dialog. After locating versions, users can right-click on a version in the list box to open a shortcut menu with available processes for the context. Users can choose a process to open its process execution dialog. The shortcut menu also includes Print and Save options.
- Additional options to build a snapshot view have been added, including:
- Snapshot View based on latest version in working view or on a given date.
- Snapshot View plus Packages.
User can select the versions contained in the snapshot view specified in the Snapshot View field, plus the packages listed in the Packages list box will be included in the new snapshot view.
- Support of empty item paths in a snapshot view
If the latest version in a working view has been reserved, the latest one with a normal tag in the trunk will be selected.
- Able to select the item paths from working view.
Able to delete a newly created version (version 0), which is generated by checking in a new item in the working view.
- Version data is stored in the database instead of in the file system. A compression option is provided to reduce space usage.
- Enhancements to the check in process:
- The local host file is not required to exist when using check in with the Release Only option.
- Able to check in by right-click on a version that has a reserved tag.
- Supports package-based check in by right-click on a change package object.
- Supports hidden files check in/out
- New process added to perform renaming of an item.
- Enhancements to the version merge processes simplify resolving conflicts.
- Options in the concurrent merge, cross project and interactive merge processes allow the user to specify how the process will execute. For example, the concurrent merge process offers the user the following options:
- Always Create Merge Version
Creates a merge-tagged version, regardless the location of changes updated by multiple versions.
- Create Merge Version Only When Conflict
Creates a merge-tagged version only when there are block of data updated by multiple versions
- Take Trunk Version
Selects the trunk version, without comparing the contents of merged versions.
- Take Branch Version
Selects the branch version as the result, without comparing the contents of the merged versions.
- The cross-project merge function now retains form association and supports a placement option to carry over the changes in either main trunk or branch.
- Support 3-way or 2-way interactive merge option.
- Show the contents of deleted line in the interactive merge dialog
- The access control bit implementation schema has been replaced with a database table column based schema to facilitate the search and reporting functions that users need. With this change, there is no limitation on the number of user groups that can be created.
- Using an object's properties dialog, access is granted to one or more user groups, allowing members of those groups to perform a particular kind of action on the object. Access can be modified whenever necessary. Selecting the Access tab from an object’s properties dialog displays a list of methods, which varies with different objects.
- Decrease the number of object access methods in the current release to simply the setup process.
- Eight objects within CCC/Harvest can be secured through access control: Harvest, projects, states, processes, repositories, item paths, items, and form types. Other Harvest objects are secured through an object to which they belong. For example, views, packages, and package groups are all secured through the project or state of which they are a part. Item path and item level access control are available.
- Through the CCC/Harvest agent component, users can navigate remote file systems (for example, UNIX, MVS) from local Windows environments. Users can execute check in and check out processes on remote files in MVS or UNIX from a CCC/Harvest client on Windows or NT.
- MVS platform support provides an ISPF check in/out interface for MVS-only developers.
- To support the porting of an application from client/server to mainframe, a hierarchical directory style filename-mapping algorithm is available for operating between NT/UNIX and MVS.
- A login option enables user name validation without case sensitivity.
- Adopt Microsoft Visual Studio look and feel style including multiple tabs for workspace area, multiple document list view in the right hand side pane, task bar area for plugging user-written scripts. Ease of use is greatly improved. Right-click menu is available on all objects.
- Output window shows summary of files check-in/check-out, package operations, and uses color for error lines.
- Progress status bar displays for long operations (for example, loading data into a repository).
- The usage flow can be lined up with the idea of personal visualization needs. In the tool bar, user can click on package icon to pop out the required package list information (for example, TO DO list). Then with the simple right-click, user can operate the needed package operations (for example, promote, approve). With the version icon in tool bar, user can retrieve the versions that match the search criteria. Then, user can right-click on the version object to operate version functions without navigating the Harvest data.
- Version comparison icon is available in the toolbar. User can drag any version in CM and drop on the version comparison dialog as well as drag the files from Windows Explorer.
- Server component - WinNT 4.0(sp5, sp6), Win2000(sp1), Solaris 2.5, 2.6, 2.7, 2.8, AIX 4.3.3
- Database component - Oracle 8.0.5, Oracle 8.0.6 or Oracle 8.1.6
- Agent component - WinNT 4.0(sp5, sp6), Win2000(sp1), Solaris 2.5, 2.6, 2.7, 2.8, AIX 4.3.3
- Client component (GUI) - Win95, Win98SE, WinNT 4.0(sp5, sp6), Win2000(sp1)
- Command line - Solaris 2.5, 2.6, 2.7, 2.8, Win98SE, Win95, WinNT 4.0(sp5, sp6), Win2000(sp1), AIX 4.3.3
- MVS ISPF interface - OS/390 2.5
- Added a number of new command-line and new features to existing command-line:
- User can check out/in to/from any remote machine that runs Harvest agent process
- haccess: to get the report of object access setup in project. In the future, you will be able to update the access through this utility.
- hap: to execute Approve Package process
- har: to archive projects
- hcmpview: to execute Compare View/List diff process
- hcpj: to copy a project
- hcropmrg: to execute Cross Project Merge process
- hdv: to execute Delete version process
- hexecp: to execute a program
- hlv: to execute List Version process
- hmvpkg: to execute Move Package process
- hpg: to maintain package group including create, update and delete
- hri: to execute Remove Item process
- hrnitm: to execute Rename Item process
- hrt: to restore archived project
- htakess: to execute Take Snapshot View process
- hup: to update the properties of package
- husrmgr: to maintain the user information in Harvest. This is very useful if you have a large amount of user information need to update
himpenv, hexpenv will be available in the next product update.
Version Control Interface (VCI)
- Integrate with Microsoft Visual Studio: VC++, VB
- Integrate with Visual Café
- Integrate with IBM Visual Age Java 3.5
- Documentation is available.
Additional Miscellaneous Features
- New Harvest server management algorithm is able to effectively manage the requests from Harvest client. Instead of statically starting up a number of server processes, it dynamically brings up a new server process if needed and shuts down the process when the process is idle for certain period of time. In addition, each Harvest server can provide the services for multiple client requests.
- Optional report generation using user-written VB or Java scripts. In the Harvest workbench, user can invoke the Project package distributed report through invoking a report icon in the taskbar area. While in the Harvest Administrator interface, user can invoke a sample Access report in the taskbar that invokes the command line haccess and shows the results on the screen.
- The new RTMON is a GUI tool that enables users to monitor the communication between client, broker, agent and server processes. Information on who is using the CCC/Harvest services from what machines is shown.
- Interface with LicenseIT for the license control.
- Support internationalization
Web Client (Will be available as a separate release)
- Web client that supports Harvest end user-centric functions including:
- Navigate the life cycle, change package-related information, and locate the change packages, forms or versions based on the same search criteria on GUI
- Create change package and edit form
- Perform package operations: promote, demote and approve/reject
- Perform package group operations: create, delete, bind packages, promote, demote, approve/reject
- Package-based check in
- Item/version operations including rename item, remove item, list version, delete version, concurrent merge functions
- Package-related reports
Upgrade From Previous Release
- Migrate from previous CCC/Harvest versions (Refer to the GSG for detailed information.)
- Due to the architecture change for this release, user needs to define the upgrade plan to assure the successful transition. Utility is provided to calculate the data storage needs based on your current usage and your estimate for future requirements.
- There are steps to upgrade including metadata, repository for change data, and clean up. Log files are generated in every step. User can either execute step-by-step or let it operate automatically.
- Custom form conversion program is provided.