cancel
Showing results for 
Search instead for 
Did you mean: 

Suggestion on NWDI upgrade

Former Member
0 Kudos

Hi Experts,

We are upgrading our portal from 7.0.2 to 7.4. We have some portal components developed using NWDI 7.0 are used in portal.

We have installed new NWDI 7.4 server rather upgrading NWDI 7.0 server (Basis confirmed so).

Now I need to know the steps to migration portal component developed in NWDI 7.0 server to NWDI 7.4 server.

I know the steps to migrate project between tracks in same NWDI server but I have not done migration of tracks from one NWDI 7.0 server to another NWDI7.4 server.

Also please let me know if this is a complex scenario we should not follow or something.

Thanks,

Karthi

Accepted Solutions (1)

Accepted Solutions (1)

former_member189220
Active Contributor
0 Kudos

Hello Karthi,

First and foremost, you do not to upgrade the NWDI to 7.4 in order to transport your changes to RTS which is 7.4.

0.

What is needed to be 7.4:

* RTS (which you have),

* the versions of the SC in development configuration track,

* the NWDS where you will create (eventually your new customizations for 7.4) needs to follow the rule in note 718949 - Web Dynpro Application Compatibility WebAS SPx -> SPx+n (hopefully you do have access to the Service Market Place in order to be able to read notes)

I would recommend you also this nice article which explains in detail this matter regarding the used versions:

http://scn.sap.com/community/nwdi/blog/2014/03/26/nwdi-vs-nwdi-content

1.

Next, the migration process is not something so complicated. What you need to do, is to get the SCA of your customized Software Component from NW 7.0 and make it available in the defined transport folder in the CMS - Domain Data >>> Transport Directory:

Very important point here is - before make an assembly make sure there are NO OPEN activities on your NW 7.0 NWDI dev.conf. track. (from where you will get the SCA with the customizations)

It is also a very good idea to perform checkDB (check for database inconsistencies in DTR database). Here would help

1447272 - Support commands in the DTR console (checkDB for inconsistencies)

and this guide:

Help for DTR console

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/49/12b42a9ba4105ee10000000a42189d/content.htm

2.

You have to defined Product in SLD. There you will have to define yours SC.

After that 'add' this product in CMS - Landscape Configurator.

Make an Import in Transport Studio - Dev.

Again before you can do any import in (dev, cons, test or prod) you need to get the SCA added to the queue…

… adding to queue can happen in different ways:

1. check in

2. forward from antoher track

3. track connnection

4. …

If you stay with the option only 1 NWDI server - you do only need to either connect the tracks or do a forward. Forward is the better approach as you probably do it only once.


Else, in the case of 2 NWDIs, you take the 7.0 custom SCA and put it to inbox of the other NWDI and check it in into a 7.3 track. Afterwards it can be "changed/migrated" in NDWS to do the migration.

3.

Then, provided you do not have any errors in CBS and/or DTR, you might import this track in NWDS in order to make additional customizations for NW 7.4.

The rest of the process is similar to that in NW 7.0.

Create DC, 'refer' it ot Activity. Activate and Release.

Then Consolidate and eventually deploy.

4.

I believe you might find useful the following documents:

Migrating Tracks Content from SAP NetWeaver 7.0 to a Higher Version

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

Creating a Development Track

http://help.sap.com/saphelp_nw73/helpdata/en/49/10d5313d9d132ee10000000a421937/frameset.htm

Forwarding Software Component Archives

http://help.sap.com/saphelp_nw73/helpdata/en/49/1bffaa23d83894e10000000a421937/frameset.htm

---------------------------

Migrating Web Dynpro Java Applications from SAP NetWeaver 7.0 to Composition Environment 7.1:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/40af00ad-8080-2a10-88b5-cc4cec99d...

Migration of Web Dynpro Java DCs from 7.0 to 7.31 – Stepwise procedure and troubleshooting

http://scn.sap.com/community/web-dynpro-java/blog/2013/02/22/migration-of-web-dynpro-java-dcs-from-7...


"MIGRATING APPLICATION PROJECTS FROM SAP NETWEAVER 7.0 TO A HIGHER SAP NETWEAVER VERSION"

http://help.sap.com/saphelp_nw73/helpdata/en/48/257a6142ac539ae10000000a421937/frameset.htm

Good luck!

Milen

Former Member
0 Kudos

Hi Milen,

Thank you for the detailed explanation it helped a lot.

I have other query , if we migrate the custom SC from 7.0 track to 7.4 track all the content in old SC will be removed from old track right?

Because I remember in my earlier projects we lost the old custom SC content after migration. Is there any way we can avoid that to keep a backup until we fix the migrated code in new track?

Thanks,

Karthi

former_member189220
Active Contributor
0 Kudos

Hello Karthi,


When you assemble in the NW 7.0 track you get an SCA.

Your customizations are in this archive. I believe it is a kind of backup.

Next when you import them in NW 7.4 track your NW 7.0 customizations should be there again. What is more, they should be visible when you import the NW 7.4 track in the NWDS.

Then in the NWDS you have to make a migration - for the DCs. You might add a new DCs to NW 7.4 track in NWDS as well (but I'm sure you are aware of this).

Having said this, I need to warn you that some SAP software components do not follow this migration procedure. This is due to they are delivered with the Source Archives, f.a. CRM, MSS, ESS and as far as I know BI too (but for the latter I'm not completely sure). Hence they are delivered with source files you will have to create your customizations manually in NWDS (create the DCs again).

Example for ESS...

ESS 603 and ESS 633 are completely independent packages. A migration is not possible here. Hence any modification you have done on ESS 603 is specific for ESS 603 and can NOT be migrated to ESS 633 . More concrete:

ESS 603 is the package for < NW7.3

ESS 633 is the package for >= NW7.3

Of course for ESS, customiziation concerning iViews, roles, pages are part of the Business Package - hence no need to 'migrate' - as it is still the same. However, all other parts can't be migrated, as these are two separate application packages for separate NW releases. For these you have to do it manually - recreate the DCs in the NWDS.

Please consider the type of application you are trying to migrate and post your questions in their SCN discussion space.

Hope this helps.

Milen

Former Member
0 Kudos

Hi Milen,

I wanted to confirm taking SCA as a backup is the right thing.

Thanks for confirming it.

Just for your information I am not migrating ESS/MSS. It is a custom abstract portal component project.

Regards,

Karthi

former_member189220
Active Contributor
0 Kudos

Hello Karthi,

I just gave the ESS as an example ('cause these applications might be accessed through portal).

Anyway, please do not forget to refer to this note

1572743 - Required SCs for Specific Type of Development in 7.31 Track and 7.40 Track

and define the correct SCA dependencies in SLD for your product.

In the note you might find that the necessary SCs for 'EP development' are:

(in section Enterprise Portal (EP))

COMP_BUILDT

ECM-CORE

ENGFACADE

ENGINEAPI

EP_BUILDT

EP-BASIS

EP-BASIS-API

EP-RUNTIME

FRAMEWORK

SAP_BUILDT

WDEXTENSIONS

WD-RUNTIME

WD-RUNTIME-EXT

Regards

Milen

shravan237
Member
0 Kudos

Hi Milen

We are upgrading NWDI 7.4 to NWDI 7.5 , Can you please let me know what are the pre and post steps for NWDI upgrade .

do we need to creatr track ID ? or anythind sequence we need to follow

Thanks in advance

Regards,

Shravan

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Milen, Since we had installed NWDI 7.4 we decided to created track in new NWDI 7.4 server. We followed below steps to migrate old track to new track • Exported Product and software component from old nwdi server • Imported the product and SC to new nwdi server • Pasted old SCAs in new CMS inbox • Created  new track in 7.4 • Added SC in new track • Updated CMS inbox • Imported track in NWDS But I couldn’t find any dc under my old custom SC.I can see dcs under standard SC Please let me know if I missed anything Regards, Karthi

former_member189220
Active Contributor
0 Kudos

Hello Karthi,

1. Your SCA has to be marked as "To be Developed". Otherwise the NWDI will not know that this SC contains source files.

2. Make sure the SCA is in the transport folder you define in CMS - Domain Data.

Also make sure that the same file structure below your SCA is kept in the NEW CMS inbox.

Regards

Milen

Former Member
0 Kudos

Hi Milen, 1.My SCA is marked as "Developed" does this mean it is marked as "To be developed"?? 2.My SCA is kept in the transport folder defined in CMS - Domain data defined path -/usr/sap/sid/JTrans. We kept SCA under /usr/sap/sid/JTans/CMS/Inbox 3.Im not sure of this point " make sure that the same file structure below your SCA is kept in the NEW CMS inbox". SCA is a compressed file right? how can I check the file structure of SCA?? Thanks, Karthi

former_member189220
Active Contributor
0 Kudos

Hi,

Is your component successfully imported in CMS - Transport Studio - (tab) Dev?

Do you have any problems in CBS? (f.a. Broken/Dirty DCs)

Regards

Former Member
0 Kudos

Milen,

In CMS-dev tab I cant see my custom component but I can see all standard component.

But in CBS I can see my componenet but "Total DCs"  column is zero.

I belive this must be the issue.

Because of this when we navigate to DTR web ui we don't see any content inside my SC.

Thanks,

Karthi

former_member189220
Active Contributor
0 Kudos

Hi,

Your component has not been imported. In this way no development might take place in NWDS.

We will have to check it step-by-step...

Please post a screenshot displaying CMS - Landscape Configurator - Track Data.

What is interesting is the SC dependencies that are displayed.

Next please execute Change >>> Synchronize SC dependencies. Please check whether your data is different between CMS and SLD definition. It is possible that you have it correctly in CMS but it is not defined in SLD. NWDS takes the information from SLD.

Regards

Former Member
0 Kudos

Hi,

As you mentioned my component might not be imported.

Hence we tried to recreate the track and reimported all SCA .

Now I am able to see the DCs in NWDS.

But Create project option is greyed out in NWDS.

former_member189220
Active Contributor
0 Kudos

Hi,

PRT_UTIL (and any other SC where will take development) should be marked as Developed in CMS - Landscape Configurator when you add them in Development Configuration track.

Regards

Former Member
0 Kudos

Hi Milen,

I was saving for the last Thank you so much for your timely support.

We knew we have to choose the developed in CMS but forgot the checked it. Now we marked our custom component as develop and I am able to create project in NWDS.

Thanks,

Karthi