DTR - Return to a previous version of an application and assign it as the last version

[Former Member]

We need to manage the code WD Java application that we are developing using DTR.

To show what we need, I'm going to create an example:

- There is a WD Java application with version "v1.0" in Production system
- There is a version "v2.0" of that application in the Development and Integration systems
- Suddenly a modification must be done urgently about the same application and the client wants to transport this modification to Production before than  transport version "v2.0".
- Therefore, we need to move to development version 1 ("v1.0") which is currently in production. To do that, we can get on DTR that version using "Sync to Date" selecting the date that the DTR had that version ("v1.0")
- We already have that version but we can not change it because we can only modify the latest version ("v2.0").

Could we assign the "v1.0" as the last version in the DTR in order to modify it?

Could you help us?
Thanks a lot!!

Regards.

[Stefan-EA · Accepted solution]

In order to avoid this in the future, you must setup a three track system which will allow you to do concurrent NWDI development. Please go over this SAP best practice blog which goes over this setup.

The following may or may not work, but I think you may be able to salvage the situation by implementing this best practice using your existing development track. Make sure you are comfortable with the SAP blog and related NWDI documentation first.

Go to the Landscape Configurator, select the existing development track where the V1.0 SC is (Lets call this track DEV) and click on "Save As" to create a new track called MAINT. Add the portal runtimes and any build variants that are needed. Go to the Transport Studio and import the required SCs in this new track (eg BUILDT, JTECHS,etc).

Go to the assembly tab of the DEV track where the V1.0 SC is and click on "Forward from History". Set the Target Track to your new maintenance (MAINT) track and select "Assembled in history" and change the Time Frame to "All". You should now see your V1.0 SC that is in your production system. Select it and then click on Forward.

Now go to your maintenace track and import the forwarded V1.0 SC. With NWDS, validate that you have the same code as in the production system.

If the code is valid, create the PRD track as per the blog. When creating this track, the "Design Time Repository URL" and "Component Build Service URL" must remain blank.  The custom SCs must also be added as required SCs and not developed SCs. To validate that this track has been created correctly, make sure there it contains no assembly tab.

The final step is to add the track connections. Add the following connections in the Landscape Configurator under the Track Connections:

DEV -> MAINT: Transport

DEV -> PRD: Transport

MAINT-> PRD: Transport

MAINT-> DEV: Repair

If the above worked correctly, you can make your change to the 1.0 code (lets call this V1.1) in the MAINT track and push the change to production. This change will also auto propagate to the DEV track once you approve it in the Approval tab in the MAINT track.

Then import this change into the DEV track. This will cause a conflict in NWDS, which will need to be resolved by the developer in the Design Time Perspective. The developer will then have the option to accept the change (ie V1.1) into the 2.0 code or reject it.

Development of SC 2.0 can continue and it will also contain the V1.1 change.

[Former Member · Accepted solution]

Hi Stefan,

Thanks a lot for your help !!!!

Best regards.