Java Development with DTR as Central Storage for the Source Files 

In this scenario you use the SAP NetWeaver Developer Studio for development, and from the SAP NetWeaver Development Infrastructure (NWDI) you use only the Design Time Repository (DTR) for storing and versioning the source files of the project.

In this scenario you do not use development components (DCs) development. You can use this development scenario if you cannot or do not want to make use of the SAP component model.

The Java development with a central storage for the source files supports Java and Java EE development. This provides unlimited support only for purely Java and Java EE projects. No DCs in the sense of the component model are used.

Prerequisites

●      The AS Java with NWDI for the DTR service is installed.

●      The Developer Studio is installed on every developer PC.

●      (Optional) The AS Java for the central test server is installed.

Activities

The following figure summarizes the various players of a team-oriented development and how they interact:

 

Development

As a developer, you create Eclipse projects and perform development using the Developer Studio. The SAP libraries you need for compiling applications are pre-installed together with the Developer Studio. You can compile applications and assemble the development locally using the Developer Studio.

In order to share source code with other team members, you use the DTR, again from the Developer Studio. The DTR provides a central files and folders based storage of sources, versions history and concurrent work on resources in a controlled manner. With the DTR you work easily in the team with other developers.

You can easily integrate the DTR with a conventional script based environment, since sources can be replicated to the different developer’s local file systems. You can then write your own build scripts to compile and assemble the projects. A developer can also install a local AS Java for testing.

With the Developer Studio you can trigger the deployment of the applications too.

Quality Management

As a quality manager you can maintain different states of source code in the DTR, for example, for development, consolidation or testing and production, by creating distinct DTR workspaces in the repository. The DTR workspace concept is similar to the code linesor branches in other version control systems.

By defining roles and permissions for various resources in the repository, the quality manager controls which developers can participate in a project and create or change sources.

The DTR can easily be integrated with a script based, automated central make environment. For that, a command line tool allows you to replicate sources from the repository to a central make server and run customer defined make scripts. To allow consistent testing, a central test environment may be established.

For the productive use of the different applications, you have to define a system landscape consisting of DTR workspaces and AS Java instances with different roles – development, consolidation, test and production.

In addition, you have to establish a software change management process that defines rules for releasing changes, controls the transport of changes between various workspaces of the repository, and manages the deployment of the application into the different AS Java instances. All tools necessary for transporting sources between workspaces and repositories are provided by the DTR.

Scenario Workflow

Configuration Steps

To configure development with DTR as a central storage for the source files, you have to:

...

       1.      Configure the DTR.

                            a.      Configure the user management system and create the users and authorizations.

                            b.      Create workspaces in the DTR using the DTR command line tool.

See Creating Workspace Folders.

       2.      Configure DTR client definitions for all instances of the Developer Studio.

See Managing DTR Clients.

       3.      (Optional) Implement manual or automated processes for change management.

Development Steps

...

       1.      Create projects using the Developer Studio.

       2.      Download the required sources to the local file system.

       3.      Change the source code.

       4.      Build it locally.

       5.      Deploy and test in a local runtime system.

       6.      Release the changes in the DTR. With this the changes become visible for other developers.