how to define track connections?

[Former Member]

We have 2 landscapes and each landscape has 3 systems (DEV, QA, PRD)

Any development done on the DEV of the first landscape should be transported to all other

system if this development is approved.

When define the track connection , we have to follow this sequence

DEV(1st landscape)->QA(1st)->DEV(2nd)->QA(2nd) ->PRD(1st) ->PRD(2nd)

At the same time, DEV(1st), QA(1st), PRD(1st) must be in their own track, while the rest

systems are in the 2nd track.

Please help advise how to define above track connection?

Thanks!

[Former Member · Accepted solution]

Hi Christy,

With normal CMS transport you can not achieve the transport route that is in question. You need to do some workaround to achieve this:

Configure track according to your need that is DEV(1st), QA(1st), PRD(1st) in first track and DEV(2nd), QA(2nd), PRD(2nd) in 2nd track.

After development in DEV(1st), import your changes to QA(1st). After successful test in QA(1st) go to approve tab of CMS transport studio and approve. Now the SCA is ready fro import into next track as well as the PRD(1st). At this moment do not import changes into PRD(1st).

Now switch to 2nd track and import SCA into DEV(2nd) and QA(2nd). Switch back to 1st track and import into PRD(1st). At the end import into PRD(2nd).

Yes, this looks bit weird, may be you can wait for others opinion on this.

For cleaner solution, I would say use CTS+ for transport. With CTS+ you have more flexiblitity of creating transport route in the way you want.

Refer to following link for more details:

<<http://help.sap.com/saphelp_nw04s/helpdata/en/47/18690079283125e10000000a1553f7/frameset.htm>>

Regards,

Bhagya

[Former Member · Accepted solution]

Dear Bhagyalakshmi :

Your solution is exactly what I want.

However, would you please inform me how to define the track connection so that what you

said would happen?

May I simply define

track one: DEV (1st), QA(1st), PRD (1st)

track two: DEV(2nd), QA(2nd), PRD(2nd)

then define the track connection = track one=>track two

Then what you said would happen? i.e. once it is approved for PRD(1st), it will be ready for import

into DEV(2nd)?

I am afraid that "track connection = track one=>track two" means only AFTER the import into

PRD(1st) is done then it will be ready for DEV(2nd).

Please confirm, thanks!

[nitin_mahajan2 · Accepted solution]

There is a "Forward from history" option in NWDI Track approval tab.

Click it, chose the track you want to forward the SCA to, the SCA you have approved and want to forward to, and send it to the track

It will go like

Track1 : Dev > QA > Approve > Track 2: Dev > QA > Approve to Prod and Import

At this time you can send it to CTS Plus to deploy on different production servers.

~Nitin

Edited by: Nitin Mahajan on Jun 16, 2009 8:06 PM

[Former Member · Accepted solution]

I do not see the option called "Forward from history".

Would you please direct me a bit, then I will mark this question answered.

Thanks a lot!

[nitin_mahajan2 · Accepted solution]

I am using NWDI 7.0 SP18

On Approval tab in CMS, there is a button Forward from History

Here is the list of buttons that i get:

Approve - Reject - Details - Select ALl - Refresh - Forward from History - Download to Excel - Export SCA - Go To History

you can contact me on my two communication ids in my business card.

Regards,

Nitin

[Former Member · Accepted solution]

Hi Christy,

Yes, once it is approved for PRD(1st), it will be ready for import

into DEV(2nd). There is no prerequisite of import into PRD(1st) is required for it to be ready for DEV(2nd).

There is no need to use 'Forward from History', if you have track connection.

Regards,

Bhagya

[Former Member]

Christy,

check this blog /people/guenter.schiele/blog/2005/12/21/best-practices-for-running-the-nwdi

Thanks

Bala Duvvuri