Hi,
the DTR is the repository - the physical storage of your files, but you actually create the development track in the CMS. Also you will find the "Transport" functionality in the CMS, which does allow you to import SCA files from the local file system. There is a specific directory, where you have to drob all your files and thereafter it will directly show up in the NWDI->CMS->Transport screen on the check-in tab.
- check after import the CBS screen to make sure, that all required SCA files are imported. If not, you will find a lots of broken DCs on that screen for your development track and you have to find out in the log files, which SCA is still missing -
Not sure if your development track is called "CRM" or not, because you can give it any name. Please ignore the <track-name>_con track always (in case you have enabled it in the development track), which is the consolidation step. Gives you the possibility to change code again, but this is not required for almost 99% of the projects - it just makes everything damn complicated if you start also doing changes in consolidation, just use consolidation to import changes from development and to publish them to the test environment - my recommendation: avoid connecting your local NWDS system to consolidation!
You will have to ask your basis administrator to create a user in the UME of the NWDI. I hope the NWDI is setup to operate as SLD or at least operates as slave of any master SLD on another system, because you actually not connecting to the NWDI directly. You will enter the SLD URL in the NWDS to establish a connection hence you will need a UME User also maintained in the SLD, which can be a nightmare as SLD & NWDI do not exactly the same user as well as exactly the same password for both systems. If the SLD runs on the NWDI (slave or master), then both have the same UME hence you will be able to connect without problems if all necessary permissions are granded.
As hamandra already highlighted, go to the developer configuration perspective after you maintained the SLD URL in the NWDS perferences configuration. Press the little gray button "New /Import Development configuration" and connect to your NWDI. A list of all available tracks will show up - your development track will show up twice (development & consolidation). Choose development and import the configuration. Thereafter you can create your local projects using the inactive DCs - they are higlighted in yellow. Yellow are only those, which are defined in the NWDI development track as SCAs to be developed.
Right click on the desired DC to import the project as local eclipse project. THe system will download all code and you can start changing those.
But please keep in mind, a good developer never does change the SAP DCs directly. You should create your own custom SCA definitions in the SLD, add them to the NWDI track and create your own DCs in those. If correctly performed, then you can overwrite & enhance SAP codings on top of the vanilla code and the build process will compile your custom application (for web applications it is a EAR project, which also needs to be a custom DC). You need a little bit knowledge about the build postbuild.vm files to enable a kind of "merge" functionality - some SAP applications can be used as example as they do use that.