Architecture of the DTR

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

DTR Client

There are different kinds of DTR clients.

·        The most common things you have to do all day during development, such as check in and check out files, are done in the Eclipse-based client.

·        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.

·        Furthermore, you have access to the contents of the DTR via Web browser and any other WebDAV-enabled client.

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

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.

DTR Server

The server part handles the file versioning. It uses a relational database to store all files.

Connection Between DTR Clients and Server

All data transfer is done using the http protocol according to WebDAV and DeltaV+.

This figure shows the parts of the Design Time Repository

DTR clients and DTR servers. For the DTR, different clients are available. 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. 

WebDAV and DeltaV

SAP uses 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.

·        DeltaV supplies WebDAV with versioning support.