Skip to Content
0

WDJ Post Migration Transport

Oct 20, 2016 at 08:27 AM

33

avatar image
Former Member

Hi Gurus,

I've been working on migration of WDJ custom applications after EP upgrade 7.0 to 7.4.

Since I'm not a WDJ guy but still I've management to do this work and have some confusions for which I require your help.

All the migration activities were done successfully and since there was a time crunch so I had to manually deploy the migrated applications in all the servers DEV/QA/PROD using the deploy option in NWDS(Webdnpro Perspective)

Also one reason to this was that while migrating the files checked out we stored in a Default activity but later on I didn't se any such activity to checkin and use the standard transport feature.

Since these developments are on a local PC and in future there would be issues if the PC gets corrupted and any future development is required

As of now I have created activity by selecting the TEAM>EDIT>Files in Subtree option when we right click on the DC in Webdynpro Perspective.

Further I'm planning to Check-IN these and Activate and then then move the developments up to consolidation and leave.

Please suggest whether this approach would be right or how can it be done.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Milen Dontcheff
Jul 12, 2017 at 08:12 AM
0

If it is not too late to answer on your querry, I would like to post some comments:
1.
"... All the migration activities were done successfully and since there was a time crunch so I had to manually deploy the migrated applications in all the servers DEV/QA/PROD using the deploy option in NWDS(Webdnpro Perspective) ..."


This might be done much more efficiently with CMS or TMS - CM Services (a.k.a. CTS+). In CTS+ you might transport your changes even on activity level. In addition the option Source Export allows you to change the code on TEST and even PROD phase.
More details about the advangates in using CM Services, you might find in this document:
How To... Configure CM Services in SAP NetWeaver 7.3 and Up
https://scn.sap.com/docs/DOC-51948

2.
"... Also one reason to this was that while migrating the files checked out we stored in a Default activity but later on I didn't se any such activity to checkin and use the standard transport feature. ..."


It is always better to name every activity. Using "default" as name for activity is not a good practise. This makes very difficult to track the activities in the DTR and with this it is also more difficult to solve conflicts.

3.
"... Since these developments are on a local PC and in future there would be issues if the PC gets corrupted and any future development is required ..."
"... Further I'm planning to Check-IN these and Activate and then then move the developments up to consolidation and leave. ..."


You are right - anything might happen with this PC. Besides, you might not use this code directly in the NWDI. It is better to Check-In, Release, Activate, Consolidate and ASSEMBLE this code.
After the Assebly you will have a SCA which you might export and store somewhere, in case something happen with the NWDI.
What is more, once this Assebly is done, you might use Track Forwarding and Production Tracks for Deployment to Multiple Production RTS. In this way it will be much easier for you to connect to another track(s) where you will migrate these changes or where you will deploy them to multiple TEST PROD systems if this is necessary.

More about Track Connections
http://help.sap.com/saphelp_nwce72/helpdata/en/49/1006fa3d9d132ee10000000a421937/content.htm

More information about Automated Deployment into Multiple Production Systems
http://help.sap.com/saphelp_nwce10/helpdata/en/42/f1a03611d83ee4e10000000a1553f7/frameset.htm


If you need some more elaborations, please let me know.

Share
10 |10000 characters needed characters left characters exceeded