Working with the Design Time
Repository
The SAP NetWeaver Composition Environment (SAP NetWeaver CE) does not come with an installation of the SAP NetWeaver Development Infrastructure (NWDI), but you can use the functionality of NWDI if you have access to a system with an already installed NWDI. In this section, you can find information about the Design Time Repository (DTR) server, which is a part of the NWDI, as well as information about working with the Design Time Repository perspective (the DTR client). You can use the Design Time Repository perspective (the DTR client) with other systems than the DTR versioning systems.
The information is divided into the following parts:
The DTR of the NWDI provides a versioned storage of the source files in a database. As part of the NWDI, the DTR runs as a service on the AS Java. It is seamlessly integrated into all development processes: as a developer you can access it using the SAP NetWeaver Developer Studio, and the Component Build Service (CBS) retrieves the source files directly from the DTR. The objects in the DTR are mainly managed directly in the Change Management Service (CMS).
You can use the DTR in all development scenarios of NWDI.
○ Version and change management
The version and change management of the DTR defines how you work with the development resources that a software component (SC) consists of. In a multi-user development, where more than one person can work with the same resource(s) simultaneously, this has to be handled in an alternate development path. In the DTR, the configuration management logs all changes to files and folders during the development process.
The configuration management includes:
■ Managing different versions of a development resource in the same repository through version control.
■ Maintaining multiple states of a software component by workspaces.
■ Managing multiple users carrying out modifications on the same development resource through concurrency control. In the DTR, there are two possible types of conflict that may appear when working in the DTR – check-in conflict and integration conflict.
A check-in conflict occurs when the version that is being checked in to the DTR is not a direct successor of the currently active version in the workspace. The currently active version is called the Remote or the Active version. The version being checked in is called the Local or the Conflicting version.
An integration conflict occurs when you try to integrate an activity to make the contained version the active version of a workspace, while this workspace already contains a version of this file, which, however, is neither a predecessor nor a successor of the version in the activity.
■ Managing distributed development of the same resource in different workspaces, which may reside in the same repository or in different repositories present in different geographical locations.
● Concepts
Provides information about the concepts and the architecture of the DTR.
● Tasks
Information about working with the Design Time Repository perspective (the DTR client).
Contains a description of the command line tool provided with the Developer Studio.
In addition, you will find a tutorial that provides a description of the steps you have to take to work in a team environment, which is required when you share the development on a project.