Example Authorizations in the Development Infrastructure 

The following examples illustrate the authorizations required by various user groups for the server elements of the SAP NetWeaver Development Infrastructure (NWDI). The activities shown for these user groups correspond largely to those activities that are encountered in practice. If you have other user groups, adapt the authorizations according to your requirements.

You can use two special inheritance types, which suppress the regular inheritance of access rights from a directory to its subdirectories in your DTR permission settings:

●      final – specifies that the definition of the access rights for a directory level also applies unconditionally to all subdirectories. The DTR ignores any access rights defined for subdirectories.

●      ignore – specifies that a subdirectory does not take any of its access rights from higher directory levels.

The examples below assumes that you are not using these options.

Developer

Assume that a developer performs the following activities:

●      Creating and developing development components.

●      Reserving names for development objects.

●      Checking source code in and out.

●      Activating changes in the DTR and triggering the central build process in the CBS.

●      Releasing activities for transport.

The following authorizations are required:

 

Server Element	Authorizations
Name Server	LcrInstanceWriterNR
SLD	LcrUser
CBS	CBS.Developer
DTR	All authorizations and access, read, write, and checkin for project-relevant workspaces.
CMS	CMS.Display, CMS.ExportOwn

Project Manager

Assume that a project manager (including product managers, development managers, and quality managers) performs the following activities in addition to normal development activities:

·         Creating and changing product information in the SLD

·         Entering reserved namespace prefixes on the Name Server

·         Creating and changing tracks for relevant projects in the CMS

·         Administering the activities of team members

·         Importing software components; transporting change requests; assembling software component versions; confirming the release of software component versions

The following authorizations are required:

Administrators of the Development Infrastructure

The following authorizations are required:

CMS User

The following authorizations are required: