The installation procedures are covered in depth in the CASEVision/Tracker Release Notes and the IRIS® Software Installation Guide. You will need to install all of the Tracker subsystems, the CASEVision environment, and ToolTalk. The system that runs the database server needs the Tracker.sw.designer, Tracker.sw.designerLinks, and Tracker.sw.rts subsystems as well.

After you have installed the Tracker software, you will have the following PDL files in /usr/Tracker/RTS:

The Tracker.pdl file specifies the main application rtsquery; the others specify the supplementary applications corresponding to their names. The projects.h file holds project names and managers and is included by the Tracker.pdl file.

The installation process also installs the script file rtsgen in
/usr/Tracker/RTS. rtsgen generates the RTS applications, based on the PDL files.

The expression dbdir is the absolute path to your database directory. You cannot use a relative path. If dbdir is not specified, then the files are stored in /usr/Tracker/db.

rtsgen allows these qualifiers:

The specified directory now contains the Tracker.pdl file, the other PDL files, and the projects.h file; use these versions for subsequent modifications. This directory also contains the database files, which are named Tracker with various extensions appended.

The script files rtsquery, rtssubmit, rtsrespond, and rtsapprove are stored in <dbdir>/tools/bin. The help files are stored in <dbdir>/tools/help. The four app-defaults files Rtsapprove, Rtsquery, Rtsrespond, and Rtssubmit are stored in <dbdir>/tools/lib/X11/app-defaults.

tvinstall creates these links:

In addition, the on-line help database is rescanned and any currently running help server is killed.

---

Note: You can add /usr/local/bin to your directory path so that in future you need only type rtsquery to run the application.

---

You should familiarize yourself with rtsquery and the supplementary applications to see how the RTS applications accommodate your needs. For additional information on their operation, refer to CASEVision/Tracker User's Guide, RTS Applications.

The projects.h file contains placeholder values for projects and their associated managers. The actual file follows:

//
// project.h
//
// This file is included by Tracker.pdl, the RTS PDL.
// Replace the sample data below with projects you wish
// to track. Make sure to separate the project name and 
// project manager on each line with a comma and '//'
// as is done in the sample data.

// Project Name Project Manager

 PROJECT_1, // manager1
 PROJECT_2, // manager2

// No comma on the last line!
 PROJECT_3 // manager3

Replace the PROJECT_* and manager* placeholders with values appropriate to your organization. Use commas after the project names except for the last one. Use a double slash (//) to separate the manager's name from the project name. The manager's name is not used in the PDL file but is stored in the database when you run rtsgen. Here is an example of a changed projects.h file:

// Project Name Project Manager
 Acme, 			// Robinson
 Framis 			// Uyeno

The Tracker.pdl file has a number of placeholder values that you need to change.

Change the following #define statements:

#define CZAR 'root'
#define BBOARD 'root'

Set the CZAR symbol to the email address of the tracking system administrator. Set the symbol BBOARD to the email address of the person responsible for screening and assigning requests, if appropriate. For example,

#define CZAR 'Nicholas'
#define BBOARD 'Howard'

Change the placeholder values in the System field declaration and its help text:

system: one-of 
 SYSTEM_1, SYSTEM_2, SYSTEM_3 

Change the help text for the Project field.

Review the rule regarding the Due Date field for both the SUBMIT_BUG and SUBMIT_RFE transitions. They both use the rule:

due_date.is(due_date.setDefault('now +30:00:00:00'));

This rule sets the Due Date field to 30 days from the current date. Change the value 30:00:00:00 as appropriate.

Now that you have made some basic changes, you should have a feel for modifying the RTS applications. The process is the same for major changes.

When the tracking system is ready for the end users, you need to make the tools directory available to them, using NFS, rcp, rdist, or other means. The users then need to run inst to install Tracker.sw.user and Tracker.sw.userLinks. Finally, they must run tvinstall giving the tools directory as an argument to create the necessary links.