Skip to Content

Purpose

The purpose of this document is to provide detailed technical instructions to configure the NWDI tracks.

 

Scope and Applicability

This document applies to the following:

– NWDI tracks for normal run and support

– NWDI tracks setup during backend upgrade (if any portal systems connected to the system which is getting upgraded)

Instructions

General Track concepts

  • Traditional track setup (as CONS workspace might
    be required)
    • Using 1 single track is sufficient
      • Development
      • Consolidation
      • Test
      • Production  

        

Different track setup possible (e.g. for separation of transport permissions)

 

Pros:

 

  • Local deployment testing on multiple systems possible
  • First integrated version available on HRD system (immediate deployment after CBS build)
  • Milestones / known good versions to be released and imported into Consolidation à first system for real tests

Basic single track configurations

Basic single track configurations.jpg 
 
As you can see all the system are configured in single development track.  After the assembly the changes automatically goes to test system for import. Here it is very unlikely to control in case any transports got assessable unintentionally. In most cases, a single track is sufficient. During development of the next
version in DEV, the CONS system is used for urgent bug fixes to the released version that is deployed in the production system. As soon as the new version
is imported into the CONS system, there is no longer any chance to fix bugs in the current production version. The reason for this is that the track template
does not include workspaces and build spaces for TET and PRD systems. If a bug occurs in the production system, the only way to fix it is in the CONS system and to ship it together with the new version to the PRD system.

Separate development and delivery tracks

Separate development and delivery tracks.jpg

In this approach the Development and delivery tracks are separate.In this proposal, once the assessable task is finished, we will have to forward the .SCA files manually in to delivery tracks for further imports in to test and production systems. This also gives an opportunity to have multiple development tracks and can also control bit more the manual errors.

With CTS+

With CTS+.jpg
NWDI tracks for normal run and support

The best practice for setting up the normal run and support track is explained in the below wiki.

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

NWDI tracks setup during backend upgrade (if any portal systems connected to the system which is getting upgraded)

In one of the recent project that I was working had a wired scenario and it is

 

  • Upgrade of backend system (from ECC 5 to ECC 6 EHP 6)
  • During the same time the hyper care for the frontend was happening (Was upgraded from NW640 to 7.3)

One of the proposal was given is following

 

Until Final cutover day

Until Final Cutover day.jpg

On Final cutover day

On Final cutover day.jpg

With this approach the hyper care for front end upgrade went smoothly.

How to set up the tracks

http://help.sap.com/saphelp_nw70/helpdata/en/44/355093ba830a67e10000000a422035/frameset.htm

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply