The Repository

The PowerDesigner repository is a tool for storing and sharing versioned models and other files used in your modeling process. It provides robust, granular security, and supports full access from within PowerDesigner and viewing and some administration via a Web browser.

Note: Before you can access the repository, an administrator must install and configure it and provide you with a user name and password. For information about installing the repository, see Installation Guide > Installing the Repository.

The majority of repository users:

Browse and search the repository (see Browsing the Repository and The PowerDesigner Portal)
Add and update documents in the repository (see Checking Documents into the Repository)
Check documents out of the repository to view or edit them (see Checking Documents Out of the Repository), and may also:
- Create versions to retain a history of the development process (see Freezing Document Versions)
- Lock document versions to temporarily protect them from modification by other users (see Locking Document Versions)

More advanced users will have additional rights to:

Create groups of document versions to mark particular milestones in the development process (see Grouping Document Versions in a Configuration)
Creating branches in the repository version tree (see Branching Version Trees)

Administrators take responsibility for:

Installing and maintaining the repository (see Installation Guide > Installing the Repository)
Providing access to the repository by managing rights and permissions (see Controlling Repository Access)
Providing customization of the PowerDesigner interface through permission, UI, an general profiles (see Customizing the PowerDesigner Interface)
Deploying an enterprise glossary and library of reference models and other documents to be shared with all users (see Deploying an Enterprise Glossary and Library)
Adding resource files to the repository and managing their sharing (see Sharing Resource Files via the Library)

Checking Documents into the Repository
You check documents into the repository to share them with others. You must have at least the Write permission on a document (or on one of its packages) to be able to check it in.
Checking Documents Out of the Repository
You check out documents from the Repository in order to work on them in your local workspace. You must have at least the Read permission on a document (or on one of its packages) to be able to check it out.
Checking the State of a Document
PowerDesigner monitors the state of your local document versions against those stored in the repository. A small icon is displayed before the document name in the Local tab of the Browser and, if you select the document, its status is displayed in the status bar.
Browsing the Repository
The PowerDesigner repository can contain various types of node.
Freezing Document Versions
Unlike many repository systems, the PowerDesigner repository does not require you to create a new version of a document each time you check it in. You create a version only when you want to, by freezing the document.
Deleting Documents and Document Versions
If you have the Full permission on a document, you can delete the most recent version of the document or delete the document (and all its versions in all branches). Deleting a document version allows you to go back to a previously frozen state.
Locking Document Versions
You can lock a repository document to prevent other users from making changes to it. Only you or a user with the Full permission on the document can check in changes to the document until you unlock it. Generally, you will release the lock when you check in the document.
Grouping Document Versions in a Configuration
A configuration is a container for grouping a set of repository documents versions together to mark a particular point in a project, such as a release or other project milestone. You must have the Manage Configurations right to create configurations.
Branching Version Trees
Users with the Manage Branches right can create branches in the repository to support concurrent development of multiple versions of documents. You can use permissions to control access to individual branches and integrate changes made in one branch into another.

Parent topic: The PowerDesigner Interface