Skip to Content
author's profile photo Former Member
Former Member

NWDI track sync/connection

Hi,

I have a question about the "TRACK CONNECTIONS/SYNC".

In NWDI, we have created two separate tracks(track_DK3 and track_DK4) for DK3 and DK4 systems. We created the track connections(track sync) between these two tracks and changed the "configure check-in" to - archives directory and imported the SCAs into Dev and Cons of DK3 and DK4,So that when the developer check-in activity in DK3 system via NWDS, that will be available in DK4 track's CONS tab.

But, we are not seeing the changes coming into DH4/DK3 when the developer checks in the activity.

Please suggest.

Thanks,

Ravi

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Aug 28, 2013 at 01:09 PM

    Needless to say, make sure you read also the document

    http://scn.sap.com/people/guenter.schiele/blog/2005/12/21/best-practices-for-running-the-nwdi

    This document is also available as a link in the previously mentioned document, i.e. in http://scn.sap.com/people/marion.schlotte/blog/2006/03/30/best-practices-for-nwdi-track-design-for-ongoing-development

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 28, 2013 at 12:50 PM

    Hello Ravi,

    first of all, the Configure Check-In in CMS webui and the check out/check in action in NWDS are two different things.

    A) "Check-In" and "Configure Check-In..." features in CMS webui

    "Check-In" in CMS webui means that you have dependent SCs for your software product which you want to use for development. You do this in the CMS webui, and the meaning of this action is that this is the first moment when you decide which SP version of the given SC to work with (i.e. phisycally which SC file(s) to use for development , which you have put into the CMS inbox previously). Once the SCs are checked in on the CMS webui, the SCs are available for Import on the Development tab of the CMS' Transport studio. If you import the SCs they will be part of the DEV buildspace and after this point you can go to NWDS and trigger Development Configuration import (track_DK3_dev[<number>] in nwds), and start your development by checking out a resource (see point B).

    As you know when Checking In software in CMS webui, the SCs have to be available in the CMS/inbox folder. This is as default the location <transport folder>/CMS/inbox. Transport folder can be figured out from the Domain Data tab of the Landscape Configurator (CMS webui).

    As mentioned this is the default location, and Configure Check-in is only used if you want to use a different folder for the SCA files than the default one. This is the only feature of this function. I personally never use configure checkin only the default location, but there are scenarios where it makes sense to organize the SCA files using different folders.

    B) Check in and check out resources in NWDS

    "Check in" in NWDS means that you checked out a resource from the DTR (will be maintained in dev/inactive), you do some change on it, and when you are ready with the change and tested it locally, you check it in, so it will be populated in the dev/inactive workspace of DTR and will be available for check out for other developers. Once you activate it, it will go to the dev/active DTR workspace (prerequisite of activation that the software can be built, else it won't go to dev/active). Once it is activated it is available for release (again in NWDS), and once you release the activity in NWDS it will show up on the CONS tab of the CMS webui and is available for import into CONS space.

    Track connection works this way:

    You have a software in say track_DK3, and there you make a change (via checkout in NWDS, checkin, activate, release, import to CONS). Once the change arrived to CONS, you can make an assembly that is used to generate your custom product (SCA file). After this you import this SCA into TEST, and then comes an Approval step. Now this is important because approval has 2 main features.

    1. this is a moment where the nwdi admin can decide whether the software can go to production (i.e. here before importing to prod the nwdi admin has a chance to reject or approve the software. This is just an additional security feature making sure the software can go live to the prod system).

    2. The other feature is that once a software has been approved, AND there is a Track connection then once the change has been approved, it will show up on the Development tab of the track where it is connecting (e.g. track_DK4). Once you import it to Development space (CMS webui -- Transport Studio -- Development tab) then you can go to your NWDS and import its development configuration (track_DK4_dev[<number>]) and start development on that track (check out, check in, activate, release ,etc as mentioned above in point B).

    See also:

    Best Practices: Track design for ongoing development

    http://scn.sap.com/people/marion.schlotte/blog/2006/03/30/best-practices-for-nwdi-track-design-for-ongoing-development

    I hope this helps.

    Best Regards,
    Ervin

    Add a comment
    10|10000 characters needed characters exceeded

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.