Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Utility to identify and remove unnecessary traces

Utility to identify and remove unnecessary traces


Utility to identify and remove unnecessary traces


Heavy usage of copy\paste and cut\paste to create requirements may have resulted in the accumulation of many unwanted traces. Borland strongly encourages the deletion of unwanted traces before upgrading to version 2006 of the CaliberRM server. CaliberRM 2006 introduces traceability versioning in order to support the inclusion of traceability information in baselines. During the upgrade, your database size is expected to grow proportional to the number of traces in your database due to traceability versioning. Therefore, you should strive to eliminate any unwanted traces before performing the upgrade to 2006 in order to prevent the database size from growing unnecessarily. This article contains an SDK utility that can help you find and remove unwanted traces from your database.

***This utility is provided on an "as is" basis, without any direct or implied warranty. Borland Software Corporation has no obligation to guarantee its functionality or the integrity of the server data when it is used. You can feel free to use this utility at your own risk.

***As with any unsupported application, it is recommended that you login as the database owner and create a backup of your server data before using this utility.

***This utility has been designed to work with CaliberRM version 2005 Release 2 Service Pack 1 (8.1.534). Please upgrade your CaliberRM server to R2 SP1 before attempting to use the attached utility. In addition you will need to have installed the R2 SP1 version of the CaliberRM SDK on the client machine. Please note that attempts to run this utility with a version other than R2 SP1 will result in undefined behavior.


This utility finds and deletes CaliberRM traces for the specified set of requirements. It is a wizard-based utility that is primarily intended for identifying and removing extraneous traces that were automatically created by either tree hierarchy or copy-and-paste actions. It can also be used to delete traces for projects that are obsolete or being prepared for deletion.

This utility package contains a complete JBuilder 2006 project, including all relevant source code. The "src" directory stores the Java source code for the utility and can be used to modify/recompile the utility. The compiled .jar file and related command file are located in the root directory.

To install this utility, simply UNZIP the contents to any local hard drive directory (e.g., "C:\RMDeleteTracesWizard").

-- CaliberRM SDK
Please note that this application uses the CaliberRM R2 SP1 SDK to access the CaliberRM server. In order to run it, the CaliberRM R2 SP1 SDK must be installed on the client machine. The CaliberRM client and server components do not need to be installed, though it is often useful to install a CaliberRM client on the machine in order to test connectivity outside of the SDK.

-- Version 1.5 JRE
Please note that this utility requires that you have a 1.5 version of the JRE installed on your machine. The CaliberRM SDK installs a supported version of the JRE at C:\Program Files\Borland\Java\Sun1.5.0_03 (default install location). This JRE can be used by editing the RMDeleteTracesWizard.com file with notepad such that the full path to the javaw executable is used. The javaw.exe is located in the bin directory of the JRE installation.

-- CaliberRM SDK Utilities
Please note that this utility requires the "CaliberRM SDK Utilities" framework (version 2006 or higher) as well. Specifically, the jar file "CaliberUtilities.jar" is necessary and must be available when customizing or recompiling this application. Note that you will not need the download the "CaliberRM SDK Utilities" framework if simply plan to execute the application, rather than inspect and/or recompile the source code. The RMDeleteTracesWizard.zip archive is sufficient for those users who only wish to execute the application.

To run this utility, simply edit the "RMDeleteTracesWizard.cmd" command file as directed in the command file comments (if necessary) and then execute it from a command prompt or double click on it. One optional parameter can be supplied from the command prompt to specify the fully qualified file name of the XML configuration file (see below). Most user"s can ignore this configuration file. It isn"t necessary to use; it is simply a convenience feature.

XML Configuration File
Run-time parameters can be controlled via an XML file, by default named "RMDeleteTracesWizard.xml". If specified, this file can be used to provide default login credentials and to specify logging behavior. If not specified, default settings will be used instead. A sample has been provided and comments in the file indicate the use for each parameter. The name of this configuration file should be the only run-time argument passed to the Java class when it is executed.

Related documents:

Old KB# 15906


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:27
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.