|
|
|
|
When a database is created, you supply an empty directory for the rz_new_database script to populate. Directly into that directory the script will create the two rz_prep files, as well as a directory named RAZOR_UNIVERSE.
Below is a diagram of what will appear under the originally supplied directory. Note that the sourcing of the rz_prep file (or dotting in the rz_prep.sh file by Bourne and Korn shell users) provides users with an environment variable named $RAZOR_UNIVERSE_DIR, which leads directly into the RAZOR_UNIVERSE directory itself.
/-- DB_Compatibility1
|
| /-- ++ISSUES++
| |-- ++ISSUES++.Documentation
| |-- ++PROJECT++
| |-- Doc
| |-- Doc##Threads
| |-- Include
| |-- Include##Threads
+-- DOMAIN_01 ------+-- Lib
| |-- Lib##Threads
| |-- Server
| |-- Server##Threads
| |-- Spy
| |-- Spy##Threads
| |-- StarGuide
| \-- StarGuide##Threads
|
|-- Scripts
|
RAZOR_UNIVERSE--+-- Tables
|
|-- Weaver2
|
| /-- AIX
| |-- DIGITAL_UNIX
| |-- HPUX
| |-- IRIX
| |-- Linux
|-- bin ------------+-- SCO
| |-- SUNOS4
| |-- SUNOS5
| |-- SUNOS5.x86
| \-- Windows_NT
|
| /-- Issues_tables_templates
+-- templates ------+-- Threads_tables_templates
| \-- Versions_tables_templates
|
rz_prep--+
|
rz_prep.sh--\
If we look inside the $RAZOR_UNIVERSE_DIR, we'll see a few files which relate to the starting of a database server. These files are described elsewhere. (See "Administration files" on page 259.)
Also under the $RAZOR_UNIVERSE_DIR are various subdirectories, described below.
The Scripts directory is a very handy place to put scripts that are to be attached to various buttons, relevant to special e-mail handling, etc. The rz_prep files will place this Scripts directory ahead of the $RAZOR_HOME/scripts directory on your search path. Rather than modifying any of the supplied scripts in-place, you are encouraged to copy them into this directory for modification.
The Tables directory can contain files that are global to an entire database. For example,
The bin directory contains operating system-specific rz_db_exec executables to permit heterogeneous networks to be served.
The DOMAIN_01 directory is the top of a directory tree which actually holds the database itself.6 Under this is a subdirectory for each of the various groups under control. The names as shown above are simply examples; your directory names will of course differ. In fact, if you are using Razor only for the problem tracking aspect of the tool, you will only have the ++ISSUES++ subdirectory. The ++ISSUES++ group is the default issues group. Additional issues groups may be added at any time.
Note that for each file control group (Doc, Include... in the example above) there is a corresponding Threads subdirectory (Doc##Threads, Include##Threads...). Also, the ++PROJECTS++ directory is where all the project definition files are stored.
If we examine the structure under the DOMAIN_01 directory in more detail, we'll see a layout as shown below.
/-- Activity
|
| /-- Delete
|-- Archive --------+-- RZ_VCS
| \-- SCCS
|
/-- ++ISSUES++ -----+-- History
| |-- Info
| |-- Latest
| |-- Scripts
| |-- Tables
| \-- Updates
|
| /-- Delete
| /-- Archive --------+-- RZ_VCS
| | \-- SCCS
| |
|-- ++PROJECT++ ----|-- History
| |-- Info
| |-- Scripts
| \-- Tables
|
. --------------+
| /-- BINARY
| /-- Archive --------+-- Delete
| | |-- RZ_VCS
| | \-- SCCS
|-- Doc ------------+
| |-- History
| |-- Info
| |-- Scripts
| \-- Tables
|
| /-- Delete
| /-- Archive --------+-- RZ_VCS
| | \-- SCCS
| |
|-- Doc##Threads ---+-- History
| |-- Info
| |-- scripts
| \-- Tables
(etc., etc., etc...)
Each directory under DOMAIN_01 will have a similar set of subdirectories, as described below.
Each group will have a Delete, RZ_VCS, and SCCS subdirectory. Depending upon the archival engine selected for that group, either the RZ_VCS (for RCS) or SCCS subdirectory will be populated.
This subdirectory contains a single easily parsed ASCII file representing the attribute information for the named file, as well as a variety of supportive information. There will be a one to one relationship between files under control, and files here. For issues, the files will be a fully annotated form of the issue number (i.e. I..1-234).
This directory holds files which chronicle the changes which occur to files and issues under control. As with Info files, there will be a one to one relationship between what is here and files/issues under control.
At the time of creation, populated with rz_mail_issue_catcher and rz_query.7 It is made available as a highly localized bin for customer generated scripts. Any razor-supplied scripts that you would like to customize should be placed here - as they get executed before the distributed scripts.
Issues group directories have a number of subdirectories that are unique to its special functionality. These are described briefly below.
Files in this directory store the relationship between various issues and the development activity which was associated with them.
This directory contains two files for each of the issues in the database. Files with a `.1' suffix hold the latest representation of the text stored in the statement of problem text areas. Files with a `.2' suffix hold the text for the statement of solution text area.
|
|
|
|
|
(Part 3 of 4 for this section) (Generated 09/13/99 at 18:17:26) |
|||
|
Copyright Tower Concepts http://www.tower.com Voice: 315-363-8000 Fax: 315-363-7488 support@tower.com sales@tower.com |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |