Hi Smruti,
For every NWDI track two development configurations (_dev and _Cons) are created and not only that, each one of these configurations contain in turn 2 compartments namely active and inactive workspaces.
So your Track consists of totally.
Inactive Development workspace of your track in DTR Server.
Active Development workspace of your track in DTR Server.
Inactive Consolidation workspace of your track in DTR Server.
Active Consolidation workspace of your track in DTR Server.
Plus, for each development configurations (i.e. _Dev & _Cons), there are 2 separate Build-Spaces namely Development Build-Space and Consolidation Build-Space.
Now let's get some more clarity on what happens under the hood, when you perform the Check-In, Activate, Release & finally import your source code changes (wrapped inside the activities that you create for modifications) into Consolidation.
1) When an activity gets created as a result of any modification it's called "Open Activity". Open Activities are always associated with DTR-Client. Open activities are not available to other developers, not even for the same developer on other machine. To be more precise, Open Activities are strictly specific to the Local Machine's NWDS DTR-Client (their birthplace).
2) When you "Check-In" this activity, it implies that, all your source code modifications present in that Open Activity are copied from your Local Machine's NWDS DTR-Client to the "Inactive Development workspace of your track in DTR Server". Now that activity becomes a "Closed Activity". Closed activities become available to other developers.
3) When you "Activate" this activity, the CBS triggers a build operation to be performed on the source code modification specific to that activity present in the "Inactive Development workspace of your track in DTR Server". On successful activation, your source code will be copied to the "Active Development workspace of your track in DTR Server".
4) Itu2019s also very important not to forget that after a successful activation process, a compiled (built) form of your source code modification specific to that activity is also incorporated into "Development Build-Space" of your track.
5) When you "Release" this activity, it implies that this activity will now be available in the import queue of the Consolidation run-time system of your track.
6) When you "Import" this activity in the import queue of the Consolidation runtime system of your track, there are 2 main operations that are performed automatically,
7) In the 1st operation, CBS triggers a build operation to be performed on the source code modification specific to that activity present in the "Active Development workspace of your track in DTR Server". If the central build is successful then only the same source code will be copied to the "Inactive Consolidation workspace of your track in DTR Server" otherwise the import status will show "Import Failed"
😎 In the 2nd operation, your source code will be now copied to the "Active Consolidation workspace of your track in DTR Server".
9) Itu2019s also very important not to forget that after a successful build process explained in point 7, a compiled (built) form of your source code modification specific to that activity is also incorporated into "Consolidation Build-Space" of your track.
One main advantages of the _Cons workspace is that it never allows any inconsistent source code to be imported in it, as explained in point number-7.
In the Assembly Tab you perform the Assembly operation. In this operation a .SCA file will be generated by scanning the Consolidation active workspace. Assembly fails if during assembly operation any Broken or Dirty DC are found.
So by this mechanism, we have to be rest assured that the .SCA file that will be assembled by incorporating the modifications present in the _cons workspace will always be consistent. And the same .SCA file is transported to the TEST server for further testing.
Please revert if you need any clarifications.
Regards,
Shreyas Pandya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.