SAP NetWeaver Java Development Infrastructure

SAP NetWeaver Java Development Infrastructure, shipped with the SAP Web Application Server, is bringing the powerful SAP software logistic concepts to the Java world. Its advantages are evident for medium and small teams, but are obvious especially during the creation of extensive server-based business application that require large developers teams.
SAP Java Development Infrastructure consists of a set of closely coupled central services for the design, implementation, build and test, both in a local and in a central environment. All units are considered as the well defined components according to SAP's Component Model, improving software reusability and management of the various dependencies on application modules.
SAP NetWeaver Developer Studio: The common front-end connection to the Java Development Infrastructure of SAP NetWeaver. Application developers can easily develop, build, configure, deploy, execute and (remotely) debug applications centrally from the SAP NetWeaver Developer Studio. The Developer Studio fully supports development of components and integrates the developer's access to all services of the JDI.
SAP's component model adds information about the structure of applications to pure Java-based development. All objects of development such as Java classes stay the same but there is additional meta data added. All objects are developed in development components which define the visibility of objects and define the way objects can be reused. The component model is the basis of the new build process with the CBS.
Design Time Repository (DTR): Central storage, versioning and management of java sources and other resources with an automated conflict detection and resolution. The DTR-workspace concept separates development tasks from each other, allowing defined access for different development tasks. Its versioning mechanisms allow the synchronization of different DTR servers - this is the basis for distributed development and a modification and update concept for customers. Component Build Service (CBS): Builds runtime objects from sources ready for deployment to a central J2EE server. It performs the build based on development components on the developers' requests and automatically rebuilds dependent components requesting the required resources automatically from the DTR. Besides the build process, the CBS manages all archives needed during development. Like the DTR the CBS hosts buildspaces which are set up specifically for each development phase. The developer accesses directly via the SAP NetWeaver Development Studio.
Component Build Service (CBS): Central archive management and build processes. The CBS creates corresponding runtime objects (Java archives etc.) for Java sources stored in the DTR ready for deployment to a central J2EE server. It performs builds and automatic rebuilds of dependent components requesting the required resources automatically from the DTR. The developer can initiate the central build process directly via the SAP NetWeaver Development Studio.
Change Management Service (CMS): The CMS is used at the beginning and the end of development. First, the development environment is configured in the Landscape Configurator. The outcome of this process defines the developers' access to the central system. After the implementation is done and has been successfully tested, the second phase starts: The CMS takes the results of the build process made by the CBS and starts the consolidation, assembly, and approval of the newly developed software. The result of this is an software component archive for distribution and deployment into the J2EE server environment.