DTR Configuration Areas

Use

Security Configuration

For more information, see Network and Communication Security .
User Administration

For more information, see Authorizations in Design Time Repository .
Access Control

For more information, see Access Control Lists (ACL) in DTR
Built-in Resources

All resources of a DTR server are provided under the root URL http://<host>:<port>/dtr/ . For example http://<host>:<port>/dtr/act .

The table below shows the minimum permissions that must be granted to use the underlying DTR server functions.

URL relative to root	Description	Minimum Permissions
/act/	Collection containing all activities	Read access for <all/>
/collision/	Collection used for collision reporting	Read access for <all/>
/dfm/
/nonvresbyid/	Collection exposing non-versioned resources by object ID	Read access for <all/>
/principals/	Collection exposing principals, used by client to change password	Read access for <all/>, dynamic permission check will ensure that the authenticated principal can access a given principal only if it is identical to the accessed principal.
/prop/	Collection of all propagation lists	Read access for <all/>
/sysconfig/	Collection containing system configuration and monitoring facilities	Full access to administrators
/system-tools/	Collection containing possibilities for system configuration and system monitoring. It is structured in such a way that it shows the functionality of the different tools. In contrast to the /sysconfig/ folder, you can access this folder in the browser starting from the root folder.
/vbs/	Collection exposing virtual versions by branch ID and branch sequence number, used by client to display version graphs	Read access for <all/>
/vcr/	Collection exposing version-controlled resources by workspace ID and object ID, needed by client to access active workspace version of a given versioned resource	Read access for <all/>
/vh/	Collection exposing version history of all versioned objects, used by client to display version graphs	Read access for <all/>
/vrel/	Collection exposing version relations (edges in version graphs), used by client to display version graphs	Read access for <all/>
/vresbyid/	Collection exposing versions by version ID	Read access for <all/>
/wr/	Collection exposing all working resources, used by client for modification of open versions	Read access for <all/>
/ws/	Collection containing all workspaces	Grant permissions for workspaces which shall be accessible for the given principals
/wsh/	Collection exposing workspace history of all workspaces	Read access for <all/>
/wp/	Collection exposing the BLOB segments for export and import	Read and write access for users that perform the export or import operations in the DTR.

Note

Protect the built-in system configuration workspace /system/config/active and the configuration folders /sysconfig/ and /system-tools/ by defining appropriate permissions, which only grant access to system administrators.

Repository Display Name

The repository display name is a human readable identification of the given DTR instance. In order to define the repository display name, navigate to the following page using a Web browser and set the repository display name:

http://<host>:<httpPort>/dtr/system-tools/administration/RepositoryConfig

Background Tasks

The DTR has a built-in scheduler responsible for scheduling asynchronously-running DTR server background tasks.

List of Tasks

There are the following background tasks running asynchronously in the DTR server application by default:

UserManagerTask : Updates user groups . The DTR server keeps LRU caches for user groups to optimize performance of authentication.
AclManagerTask : Refreshes access control list cache from the database. The DTR caches all access control lists in memory in order to boost performance of permission checks done in all requests. In order to update this cache, the cached data is refreshed regularly from the according access control information persisted in the database.
DeltaVUpdateStatisticsTask : Updates database statistics on DTR tables (currently available on MaxDB and MS SQL Server only). On all other database platforms using cost-based optimization of execution plans, the administrator has to care for proper database statistics by using database tools. For more information, see your database administration manual for updating the database statistics manually.

Note
If the DTR is empty at the beginning of use, several hundreds of new objects are created or imported when it is filled. This can have a negative impact on the performance of the DRT. The reason for this is the sudden drastic increase in the database size. The Database Query Optimizer Statistics then become obsolete.

To improve the performance, you must update them. The DTR itself updates the Database Query Optimizer Statistics once a day, which is sufficient for normal operation because the percentage rate of the increasing volume becomes less as the database size grows.

Therefore, frequent updates are required only at the beginning of DTR use.
ProcessNameReservationsTask : This task is to be used if you use a name server in your development configuration. SAP NetWeaver Developer Studio will create temporary name reservations, for example for new development components (DCs), and forward these name reservations to the DTR for finalization of the name reservation when the corresponding activity containing the first version of the new DC is checked in. When this activity is checked in, the DTR will asynchronously make the corresponding name reservation permanent; if the activity defining the name is reverted, the DTR server will asynchronously revert the temporary name reservation on the name server. You may check the status of the name reservation queue in the DTR by opening the following page in a Web browser: http://<host>:<httpPort>/dtr/ws/system/config/activesupport/NameReservationList
RemovePropagatableBlobsTask : If the data that needs to be exported or imported is very large, these operations switch to a segmented mode in which the data is split up into segments. These segments are then individually imported or exported. The segments constitute temporary data and can be thrown away after the operation is completed. The task RemovePropagatableBlobsTask takes care of removing the unwanted segments from the DTR and thus frees database storage volume.

Schedule of Tasks

The schedule of all asynchronous tasks to be run is configured in the file:

http://<host>:<httpPort>/dtr/ws/system/config/active/registry/repository.properties

which is contained in the workspace /system/config/active

Note

To change the schedule, proceed as follows:

Check out this file.
Modify the task definition.
Check in the activity containing the change.

Syntax of Task Definitions

The syntax of the task definitions in repository.properties is com.tssap.dtr.pvc.util.scheduler.task<ordinal> = <implementationClass>, <startTime>, <threads>, <maxRuntime>, <interval>, <intervalUnit>, <name>, <clusterSingleton>

<ordinal> : Ordinal number of task definition, must start with 0 and increase in the order of task definitions.
<implementationClass> : The fully qualified class name of a class implemented by the task.
<startTime> : Start time 10 means 10:00 local time.
<threads> : Number of concurrent threads running this task in the same VM.
<maxRuntime> : Maximum runtime of task in seconds, when this time has expired the task will be stopped (if it didnt stop on its own).
<interval> : Task restart interval in units given in parameter <intervalUnit>.
<intervalUnit> : Interval unit as defined in calendar constants of class java.util.Calendar (SECOND, MINUTE, HOUR,).
<name> : Task name (must be unique, is used for shutting down tasks)
<clusterSingleton> :
- false : Start task on every server (VM) in cluster.
- true : Start task on exactly one server (VM) in cluster only

You can find the settings for the currently scheduled background tasks by opening the following page in a Web browser: http://<host>:<httpPort>/dtr/sysconfig/scheduled_tasks.html .

This page also shows when a certain task was last executed and when the next execution is scheduled.