Up Previous Next Title Page Index Contents

1.3 Repository Files

The repository files are generally arranged in a single directory hierarchy on a single server. The highest level directory contains one file artbase.roo that contains the names and paths of all the repositories, and a subdirectory containing each of these repositories. Initially there is probably only one repository, but later you may make backup or checkpoint repositories, copies of your main repository made at a certain time.

In a repository directory there are two files, manager.ab and trid. The manager.ab file contains the names and paths of all the areas in that repository, the names and encoded passwords of all the users in that repository, any disk name mappings needed to access the repository, and the server machine and socket number through which clients will access that repository. The repository directory also contains several subdirectories:
areas
Contains a directory for each physical area in the repository
users
Contains a directory for each user in this repository
backup
Contains a copy of the repository from the previous transaction
comm
Only created when a multi-user repository is used. Contains information about multi-user access using file communication.
As a general recommendation, repository administration and use is easiest if the server is started from the same directory as the artbase.roo file, and all client images start with that directory as their working directory. In this way all database paths in artbase.roo, and all area paths in manager.ab, can be relative paths, avoiding the need to define drive mappings or different artbase.roo files for each user. By default, MetaEdit+ uses such relative paths.

Up Previous Next Title Page Index Contents