Working with the SAP NetWeaver Java Development Infrastructure 

This section of the documentation contains the procedures you as a developer need when working with the SAP NetWeaver Java Development Infrastructure (short: development infrastructure).

For information on architecture and concepts of the SAP NetWeaver Java Development Infrastructure, see SAP NetWeaver Java Development Infrastructure.

Tasks to be executed by administrators when setting up the systems and during operation of the individual services of the development infrastructure are described under Administration of the SAP NetWeaver Java Development Infrastructure.

Elements of the SAP NetWeaver Java Development Infrastructure

The SAP NetWeaver Developer Studio provides access to the SAP NetWeaver Java Development Infrastructure. This infrastructure consists of a number of services.

·        Design Time Repository (DTR): Versioning source code management. Distributed development of software in teams. Transport and replication of sources.

·        Component Build Service (CBS): Central build based on the component model.

·        Change Management Service (CMS): Central administration of the Java development landscape and the transports covering the entire software life cycle.

·        Software Deployment Manager(SDM): Manual and automatic deployment of archives in central runtime systems.

·        System Landscape Directory (SLD): Information on the system landscape.

¡        Name Service: Central check instance for the uniqueness of names.

·        Java Dictionary: Supports the global definition of tables and data types

·        SAP Java Test Tools: Predefined static tests and runtime tests for the Java development

To configure the development environment, you use the development configuration. The import of a development configuration automatically sets the access paths fort he used services, for example, the URI of the used DTR and the corresponding access to the CBS.

You can develop in the development infrastructure either according to the component model or in Eclipse projects.

Whether you want to use the individual services for your development projects, and to which extent, depends on your development scenarios. The documentation is structured accordingly.

Development Scenarios

The development infrastructure supports the following scenarios; scenario 2 is based on scenario 1.

·        Scenario 1: Team-Oriented Development

This scenario provides unlimited support only for plain Java and J2EE projects, but not for Web Dynpro

Tools for a migration into the component model are not offered. If you later decide to use the component model, this will require a lot of manual work. Therefore, it is important to decide right from the beginning, which scenario you want to use.

There is a tutorial for scenario 1: Tutorial for Scenario 1: Team-Oriented Development.

·        Scenario 2: Development with Components.

We recommend this scenario only for demo scenarios, in which you want to test the development with the component model. SAP does not offer a spezial migration step in scenarios 2+ and 3. A migration into these scenarios at a later time must be done manually.

There is a tutorial for scenario 2: Tutorial for Scenario 2: Development with Components.

·        Scenario 2+: Development with a Track

This scenario is suited for customers who want to develop components using the full administration and build environment. All component types in the SAP component model are supported.

For a tutorial on scenario 2+ see Tutorial for Scenario 2+: Development with a Track.

·        Scenario 3: Layered Development

This scenario is suited for customers who want to develop several software components in parallel that depend on one another. SAP itself uses this scenario.

For a tutorial on scenario 3 see Tutorial for Scenario 3: Layered Development.

Using the Design Time Repository

All development scenarios use the DTR. All created or changed source files are stored in the DTR. To change them, check them out; after the change, check them in again. These frequently used actions in the DTR are integrated in such a way into the SAP NetWeaver Developer Studio that you hardly need the DTR perspective in the SAP NetWeaver Developer Studio. For these reasons, Working with the DTR is described in parallel to the development scenarios.

Using SAP Components

In the Development-Configurations perspective in the SAP NetWeaver Developer Studio, you see the development components provided by SAP (software components SAP-JTECH and SAP-JEE).

You can use these components in your applications. However, beware that SAP can change or delete their interfaces in future releases without prior notice.

If an SAP development component provides a guaranteed interface, this will be documented explicitly.

If you are in doubt concerning a certain component, contact the SAP Support with a problem message.