Buildspace for fresh development in NWDI

[former_member368258]

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 !

Regards,

Kevin

[former_member189220]

Hello Kevin,

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

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

http://scn.sap.com/docs/DOC-3204

(step3)

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:

Chen-In

Activate

Release

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

Have you done all these steps?

Regards

[former_member368258]

Hello Milen,

Thanks for reply. I did follow all the steps mentioned in the shared link. I can see that after releasing activities the new DCs are showing up only in an inactive part of 'trackname_D' buildspace , they are not shown in an active part of 'trackname_D' and active/inactive 'trackname_C' buildspace. Is there any way I can push newly copied DCs to 'trackname_C' buildspace as while importing/deploying to runtime systems its checking for archives in 'trackname_C' ?

Regards,

Kevin

[former_member189220]

Hello Kevin,

1.

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

2.

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.

Regards