Source Code Journey (NWDI under the Hood)

This article explains about how NWDI works under the hood. The article reveals the unexplained secrets and the Journey of the source code in the NWDI universe.

Introduction

Before getting started I recommend you to go through the following article to get a clear understanding between NWDI and Non-NWDI scenarios.

NWDI Empowered Landscape vs. Landscape without NWDI Setup

In this article we will unveil and explore the secrets of NWDI about its underlying core functionalities and how these functionalities are realized in NWDI universe.

The 3 Pillars of NWDI 

Design Time Repository (DTR)

A central storage for all kind of source files in various formats. It provides source code management and version control for development based on the SAP NetWeaver platform.

Component Build Service (CBS)

The CBS is the central build environment in the development infrastructure also taking care of the management of the archives needed in each development project.

Change Management Service (CMS)

The Change Management Service (CMS) represents the part of Software Life-Cycle Management in the SAP NetWeaver Java Development Infrastructure.

The Change Management Service is the central administration UI for development landscape definition and transport management.

Workspaces & Buildspaces

For every NWDI track two configurations (_Dev and Cons) are created. Each of these configurations in turn contains 3 compartments each, namely Active and Inactive DTR Workspaces, plus one CBS Buildspace.<br />So your Track consists of totally…</p><h4 class=”MsoNormal” style=”margin: 6pt 0in 0pt;”>4 DTR Workspaces:</h4><p class=”MsoNormal” style=”margin: 6pt 0in 0pt;”>Work-spaces belong to DTR</p><ol style=”margin-top: 0in;” type=”1″><li class=”MsoNormal” style=”margin: 6pt 0in 0pt; tab-stops: list .5in left .8in; mso-list: l1 level1 lfo1;”>Inactive Development workspace of your track in DTR Server.<br />(http://<host>:<port>/dtr/ws/<TrackName>/* 2 CBS Buildspaces:</h4><p class=”MsoNormal” style=”margin: 6pt 0in 0pt;”>Build-spaces belong to CBS.Go to Component Build Services (CBS) Web UI >> (Build spaces >>)</p><ol style=”margin-top: 0in;” type=”1″><li class=”MsoNormal” style=”margin: 6pt 0in 0pt; color: black; tab-stops: list .5in left .8in; mso-list: l2 level1 lfo2;”>Development Buildspace<br />”<SID>_<Track-ID>_D” build space.</li><li class=”MsoNormal” style=”margin: 6pt 0in 0pt; color: black; tab-stops: list .5in left .8in; mso-list: l2 level1 lfo2;”>Consolidation Buildspace<br />”<SID>_<Track-ID>_C” build space.</li></ol><p class=”MsoNormal” style=”margin: 6pt 0in 0pt;”>All your Source code is stored inside the DTR Workspaces and the compiled version (Built version) of that source code is stored inside the CBS Build-spaces.<br />So, when you import your development configurations in developer studio it brings the code from DTR-Workspaces and built archives from CBS build spaces.</p><p class=”MsoNormal” style=”margin: 6pt 0in 0pt;”> </p><h3 class=”MsoNormal” style=”margin: 6pt 0in 0pt;”>The Source Code Journey*

!https://weblogs.sdn.sap.com/weblogs/images/251967884/SourceCodeJourney1.JPG|height=500|alt=image|width=684|src=https://weblogs.sdn.sap.com/weblogs/images/251967884/SourceCodeJourney1.JPG|border=0!