Skip to Content

Buildspace for fresh development in NWDI

Hello Experts,

We have a new NWDI track designed with all the requied dependents software components. We want to copy few local DCs to newly developed NWDI track. To do so I have imported the new track in to NWDS however I choose 'trackname_D' buildspace while importing the track. Now I have done the DC migration from local to NWDI track but when I am trying to import DCs to different Portal runtime systems its giving an error saying no archive found to deploy in 'trackname_C' buildspace.

Did I wrongly copied local DCs to trackname_D buildspace initially instead of trackname_C buildspace ? Is there any way to import the archive using trackname_D buildspace ? Or I need to import the track again using trackname_C buildspace in to NWDS and copy the local DCs ?

Appreciate your help on this. Thanks !



Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Sep 11, 2016 at 12:43 PM

    Hello Kevin,

    Please make sure you've followed the procedure as explained here...

    Migrating Local Developments to a Centralized NWDI Environment (Developer’s Viewpoint)


    When you do copy the DC not all the work is done.

    In order your source code to be deployed successfully to the RunTime System it has to be consolidated. But before the consolidation you have to:




    the activity where this DC is. (steps 8-10)

    Have you done all these steps?


    Add a comment
    10|10000 characters needed characters exceeded

    • Hello Kevin,


      active/inactive is for DTR workspace. There is no such thing in the CBS.


      If you have activated the activity and released it, your custom component should appear in the CMS - Transport Studio - tab Consolidation. (status - Waiting for import). When you do execute import in the consolidation then a new build is triggered and then the sources will be in the active DTR workspace and the DCs will be in the CBS consolidation buildspace.


Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.