Scenario 1: Team-Oriented Development 

Purpose

You use the SAP NetWeaver Studio for development and the Design Time Repository (DTR) for storing and versioning the source files of the project. Components are not used in this scenario.

This scenario is intended for customers that for some reason cannot or don’t want to make use of the SAP component model. Common reasons may be that you as a customer already use some other third-party Java infrastructure, have to maintain existing Java code that does not comply with SAP’s component world, or want to perform a smooth step-by-step migration of legacy code.

 

This scenario supports Java and J2EE development.

Implementation Considerations

We recommend this scenario for small developer teams, for which no centralized administration is required. The development should be restricted to Java and J2EE projects.

Integration

The installation uses the SAP NetWeaver platform.

Features

Development

You as a developer create Eclipse projects and develop them with the help of the tools in the SAP NetWeaver Developer Studio. In order to share source code among the team members, use the Design Time Repository (DTR). This repository provides a central “files and folders” based storage of sources, version histories and concurrent work on resources in a controlled manner. This enables an effective teamwork among various developers. A fully featured graphical front-end for the DTR is integrated into the SAP NetWeaver Developer Studio.

SAP libraries needed for compiling applications are preinstalled together with the SAP NetWeaver Studio.Applications are compiled and assembled locally with the built-in tools of the SAP NetWeaver Developer Studio. Furthermore, the Design Time Repository can easily be integrated with a conventional script-based make environment, since sources can be replicated to the developer’s local file system. Developers can then write their own build scripts to compile and assemble their projects. A developer can also install a local SAP NetWeaver J2EE engine for testing.The deployment of applications can be triggered manually within the Studio.

Quality Management

The qualitymanager maintains different states of source code in the Design Time Repository, for example, for development, consolidation/testing and production, by creating distinct DTR workspaces in the repository (similar to “code lines” or “branches” in other version control systems). By defining roles and permissions for various resources in the repository, a quality manager controls which developers can participate in a project and create or change sources. The repository 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. In order to allow consistent testing, you can establish a central test environment. You can trigger the deployment of applications manually with the Software Deployment Manager (SDM), which is part of the SAP J2EE engine.

Software Change Management

For the productive use of applications, a system landscape consisting of DTR workspaces and J2EE engines with different roles like development, consolidation, test and production has to be defined. In addition, a software change management process has to be established, which 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 J2EE engines. All tools necessary for transporting sources between workspaces and repositories are provided by the DTR.

The following model illustrates and summarizes the various players of a team-oriented development scenario and their interactions:

 

Development environment for developer and quality manager (QM), consisting of SAP NetWeaver Developer Studio, DTR, and J2EE engine.

Prerequisites

·        The SAP NetWeaver J2EE engine with JDI for the DTR service is installed.

·        The SAP NetWeaver Developer Studio is installed on every developer PC.

·        (Optional) The SAP NetWeaver J2EE engine for the central test server is installed.

Configuration

...

·        Configure the DTR server.

¡        Configure the user management system.

¡        Create users and authorizations.

¡        Create workspaces in the DTR.

·        Configure DTR client definitions for all instances of the SAP NetWeaver Developer Studio.

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

Constraints

This scenario provides unlimited support only for purely Java and J2EE projects. No components in the sense of the component model are used.