Design Time Repository Architecture

Definition

The Design Time Repository (DTR) consists of two parts, DTR Client and DTR Server.

From the logical point of view, the DTR uses files and folders for storage. The client part of the DTR uses the local file system.

Design Time Repository

DTR Client

There are different clients you can use to work with the DTR:

·        SAP NetWeaver Developer Studio - you usually perform all common tasks with DTR using the Eclipse-based client, in the Design Time Repository perspective.

Frequently-used functions are also available in other perspectives of the Developer Studio. Individual functions such as checking out are located in the context menus. In addition, you can embed entire views, such as the Open Activities view, into other perspectives.

·        Command line client – for administrative tasks, such as integrating files from one workspace into another, can be executed in the command line client or in the administrator plug-in.

·        Web browser – you have access to the contents of the DTR using a Web browser and any other WebDAV enabled client.

DTR Server

The server part handles the file versioning. It uses a relational database to store all files. The resources are stored in a database. The resources are accessed in the context of a workspace; the versions are managed in the context of activities. 

For more information about working with the DTR, see Working with the SAP NetWeaver Development Infrastructure and Central Source File Management.

Integration

All data is transferred between the DTR Client and Server using the HTTP protocol according to WebDAV and DeltaV+.

WebDAV and DeltaV

SAP uses the open standards to communicate with the DTR server:

·        WebDAV enables developer teams to use a Web server as easily as if it was the local file server.

For more information, see www.webdav.org.

·        DeltaV supplies WebDAV with versioning support.

For more information, see www.webdav.org/deltav.