Upgrade Portal 7.0 -> 7.4 - Track versions

[nunomcpereira]

Hi experts,

we've upgraded our portal solution from 7.0 SP5 to 7.4 SP5 on our dev system where NWDI resides. I've checked that the NWDI tracks still exist as expected since it's not a fresh installation.

We don't expect to give any support to the applications until the full landscape has been migrated. Our strategy is to disconnect projects (old versions) from NWDI and if we really really need to, we deploy it directly to production.

So my question is, regarding the new 7.4 developed SCs. I intend to keep the old tracks but create a new version for our custom developments. Should i need to create a new product version on SLD? Or just a new Software Component Version with the new dependencies? Or do you suggest me not to create any new version and just remove the old dependencies on SLD and add the new ones (and then click the update cms button)?

Also, how could i disconnect the old DC versions on my old NWDS from NWDI?

Thanks in advance guys

[Former Member · Accepted solution]

Hello Nuno

I am not clear on what you  mean by how to "disconnect the old DC versions on my old NWDS from NWDI?" Please clarify on this more.

Below link should be helpful when you want to migrate track, this might not be the

use case senario you have.

http://help.sap.com/saphelp_nw73/helpdata/en/48/2f8c4856ab58d5e10000000a421937/content.htm

how to migrate track with NWDI.

kind regards

Le Li

[nunomcpereira · Accepted solution]

I'm trying to use the old tracks to handle the new SCs with the migrated versions.

This way i think that i can probably maintain the activity history as the track and DTR repositories are the same. The link you provided talks about a step where we create new versions for SCs: "Create new versions of all your developed SCs from your current track".

But then, i cannot understand why do i need to recreate all tracks (we have a lot of projects), and forward from the old tracks to the new tracks.

When i'm talking about disconnect the old dc versions i mean breaking the connection from my NWDS with NWDI, so i can't create any activities by mistake on the old NWDS. If i urgently need to correct some code during the migration, it was agreed with our customer that the code will be built and deployed from my machine directly to production until the full landscape is not migrated (i know it's not a good practice).

[Stefan-EA · Accepted solution]

Nuno Pereira wrote:

I'm trying to use the old tracks to handle the new SCs with the migrated versions. 

This will not be possible.

Assuming you will be staying on the 7.0 NWDI, you will need to do the following

• Create new SC versions with the updated build plugins in the SLD
• Install JVM 6 on the NWDI
• Create a build variant to point to the SAP JVM 6 JDK
• Create new 7.4 tracks and add the 7.4 SCs
• Add the JDK 6 build variant to the new tracks
• Forward your 7.0 SCs to the 7.4 tracks
• Migrate/update DC code if needed