Compacting a Repository
Compacting reduces the size of the repository by eliminating the following program
elements:
- All open editions
- All purged editions
- Versioned editions of classes that are contained in open editions of packages
The compacted repository, which contains only versioned editions, can be as much as 50%
smaller than the original.
The procedure for compacting a repository depends on which edition of VisualAge for
Java you use. If you use VisualAge for Java, Enterprise Edition,
skip to the instructions that follow.
Compacting the Repository in VisualAge for Java, Professional Edition
In VisualAge for Java, Professional Edition, compacting replaces the existing repository
with a smaller repository. To compact the repository:
- As a precaution, back up the repository (ivj.dat file) before compacting it.
- Version the open editions of projects, packages, and classes that you wish to
keep.
- Purge any projects and packages that you wish to discard, (To minimize the size of
the new repository, purge obsolete package editions. Purging an edition of a
project removes information about the project but does not purge any of the program
elements that it contains.)
- Open the Repository Explorer window.
- Select Compact Repository from the Admin menu. You
will be asked to confirm that you wish to replace the repository.
- Click Yes to proceed.
When the repository has been compacted, it will contain only versioned editions of
projects and packages, and versioned editions of program elements that they contain.
Compacting a Repository in VisualAge for Java, Enterprise
Edition
In VisualAge for Java, Enterprise Edition, compacting copies from the existing
(source) repository to another (target) repository.
You must be the administrator to compact a repository.
- Ask team members to purge any versioned editions that they wish to discard, and to
version any open editions that they wish to keep. (To minimize the size of the new
repository, purge obsolete package editions. Purging an edition of a project
removes information about the project but does not purge its contained packages, classes,
or methods.)
- Connect to the source repository.
- Open the Repository Explorer window.
- Select Compact Repository from the Admin menu. You
will be asked to confirm that you wish to compact the repository.
- Click Yes to continue. A dialog box will appear, asking you to
select a new or existing repository to compact into.
- Select Use shared repository and accept the IP address or host name of
the server where the target repository will reside. If you are creating a new repository,
enter its name in the Repository name field; if you are compacting into
an existing repository click Browse and select it from the list of
repositories on that server. (You may wish to compact into an existing target repository,
if someone omitted to version necessary program elements before a previous attempt to
compact the source repository.)
- Click OK to proceed with compacting the repository. Versioned projects
and packages, along with the versioned editions of their contained program elements, will
be copied to the target repository.
- Once you have a new repository that contains all program elements required by the team,
instruct all developers to change to the new repository. To check whether anyone is still
using the old one, issue the emadmin list command.
Keep the old repository on the server for a few days, in case team members need to
reconnect to it in order to export additional program elements.

Repository

Versioning a Program Element
Purging Program Elements from the Repository
Backing Up the Repository

Repository Files
