Skip to Content
avatar image
Former Member

Track connections

Hi,

I've seen that there are two types of connections: transport and repair. Normally, developments are made over a track with the four standard environments: development, consolidation, test and production.

From development to consolidation, change request are represented by activities (i.e. I have a file-level granularity). From consolidation to production, change request are represented by SCA snapshots (i.e. I have a SC-level granularity: if I decide to take the changes to the next environment I have to take all the SC).

What I'd like to have is to defer the creation of the SCA at the time of the import into the production environment, in order to keep the file-level granularity that activities have (so even in the test environment, I don't have SCA files but I have activities).

I thought of achieving this by making two tracks: the first with only development and consolidation stages linked to the development and consolidation servers, respectively; the second with only development and production stages linked to the test and production servers, respectively.

Now what I need is a way to import activites from track 1 into track 2. If I'm not mistaken the repair connection should transport activities (instead the transport connection should transport whole SCAs).

Has someone ever tried this or does know if this is feasible?
Is there a way to see, in a SAP demo or blog, what I get in the transport studio when a track connection is used (transport or repair)?

Thank you,
Pietro

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Mar 21, 2012 at 04:49 PM

    Hi,
    I have a couple more questions about tracks.

    We currently have a track with all the environments enabled: Development, Consolidation, Test and Production. Our landscape is configured as follows:

    • DEV: SDM deployment, Automatic deploy disabled, Runtime system not integrated in JSPM scenario
    • CONS: Deploy controller deployment, Automatic deploy enabled, Runtime system integrated in JSPM scenario
    • TEST, PROD: Deploy controller deployment, Runtime system integrated in JSPM scenario

    When we need to transport a change, we close, activate and then release the activity with NWDS. After the activity is released, it appears in the Consolidation tab on the transport studio.

    1) The fact that the Development tab is 'skipped' is because we do the close/activate/release activity from the NWDS?

    Let's suppose I change the landscape as I've depicted before, with two tracks instead of one configured as follows:

    1. DEV (old development), CONS (old consolidation)
    2. DEV (old test), CONS (additional test), PROD (old production)

    The tracks are connected via a repair connection from 1 to 2. Developers have the NWDS environment set up to work on the 1-DEV.

    2) When an activity from Track-1 is transported into Track-2? When it is  closed, activated and released via NWDI or when it is imported into 1-CONS?

    3) Where that activity will appear in Track-2 in the Transport Studio? In the "Check-in" or in the "Development" tab?

    4) In order to see the changes deployed on 2-DEV what will be need to do? Just the Check-In (if the activity appears in the "Check-in" tab) or the Import (if the activity appears in the "Development" tab)?

    Thank you,

    Pietro

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Pietro,

      I totally agree with Jun on this: you're running a BIG risk by trying to design some complicated thing you do not quite understand. If your NWDI is managed by an 'external group of people' and you have no NWDI expert on-site then, do yourself a favor by sitting down with this 'external group of people' (which, I expect, includes an NWDI expert) and making plans. Afterall, they'll be the ones who maintain your NWDI; if they have no idea what you're talking about or do not agree with your design then you DO have a problem :-)

      For 'emergency rollback', what's wrong with using history?

      Cheers,

      Dao

      P.S. Also, please consult this well-known blog from Marion S.

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

  • Mar 15, 2012 at 03:59 PM

    Hi Pietro,

    I'm not sure if what you'd like to have can be done. Since QA and Prod environments are not source code locations (hence, the transports of SCAs), I don't think you can (or you'd want to) 'defer the creation of the SCA at the time of the import into the production environment'. Same thing with the QA enviroment since it's supposed to simulate the Prod environment as close as possible. I figure you'd not want to have your source code in QA or Prod :-)

    The repair connection in NWDI is used for back transport as needed. Yes, you can have 2 tracks connected by a repair connection for maintenance purposes. Please refer to this link for more info

    http://help.sap.com/saphelp_nw70ehp1/helpdata/en/13/602b27f6fb41b4a9eb4f72eabb9832/frameset.htm

    Hope it helps.

    Dao

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Pietro,

      Check the 'Track Connections' link sent in my previous post and follow the link to 'Back Transports in NWDI', you'll see a figure for back transport connections.  Using this figure, for your purpose, I guess you can try to make your track #1 the 'Maintenance' track (Dev -> Cons) with a 'Repair' track connection to track #2 the 'Development' track (QA (which acts as Dev) -> Prod). There'll be no connection from 'Development' track to 'Maintenance' track. I think that might meet your requirements.

      I don't know which version of NWDI you have. As Jun mentioned, you'd probably want to check out more recent releases of NWDI for advanced features/capabilities.

      Hope it helps.

      Dao

  • Mar 15, 2012 at 04:42 PM

    don't know why you want that. seems only to complicate yourself.

    you talked a lot about "activity".

    maybe you can have a look at nwdi of ce7.2 and nw7.3, which support activity based transport.

    i haven't used that, only read some doc, don't know if that will satisfy you.

    Add comment
    10|10000 characters needed characters exceeded