NWDI Migration from 7.0 to 7.31

[Former Member]

Hello All,

We are in the process of upgrading our NWDI servers from 7.0 to 7.31 SP06. We have more than 20 tracks in the 7.0 version which are used for development. We have different types of developments going on in different tracks like Portal developments in a track, Webdynpro developments, ESS and MSS developments, Biller Direct etc. Our landscape is big where we support parallel project and production support activities in different tracks.

We would like to know what will happen to the old developments when we upgrade our NWDI server from 7.0 to 7.31. The dependent components in the latest 7.31 version is different from the 7.0 version.

1) Should we need to create new tracks and import the old developed SC into the new track?

2) We cannot change the production support track components as we need to support the ongoing production needs. What will happen to these tracks after migration to 7.31? Will it still be usable with older version of sca files? This question is specific to ESS, MSS and Biller Direct. We have made huge development changes to these tracks and need to support them until the newer migration goes live.

Thanks,

Nagarajan.

[Former Member · Accepted solution]

Hi Ervin and Stefan,

Thanks for the helpful answer. Now the next question, We have 2 Portals one upgraded to 7.3 and the other still in 7.0. Now the upgraded NWDI has tracks that were used for development in 7.0. All these custom tracks are showing as inconsistent state now. Is this because of the JDK or because of the dependent files used in the SC's.

For Ex,

Track 1 - WD Java and Portal developments 7.0 - Required this setup still because of production support environment. We cannot go to the 7.3 yet as the portals are on 7.0. But the tracks are now inconsistent. Can we have multiple tracks with one pointing to 7.0 and the other 7.3 with just the JDK version changes in the build variant? Will changing the JDK remove the inconsistency in the track? What will happen to the old dependent files in the track?

Track 2 - WD Java developments 7.0 - But need to move to 7.3 as the portal has been upgraded and the applications are broke now due to different runtime. Tracks are inconsistent here too. Should we need to just update the SC's with new dependent files in SLD and then change it in the track or create a new track with the same SC name and move the SC from old to new one?

Thanks,

Nagarajan.

[Stefan-EA · Accepted solution]

For track 1, all you need to do is add the build variant that was configured for JDK 1.4.2.

For track 2, you should create a new track for 731 and keep the old one as a reference.

Here is more info on migrating to 731

http://scn.sap.com/docs/DOC-13235

http://scn.sap.com/message/13874958#13874958

Here is a list of 731 build plugins you will need

https://service.sap.com/sap/support/notes/1572743

[Former Member]

We have successfully setup the tracks now. CBS Settings maintained as -

BUILD_TOOL_JDK_HOME =/usr/sap/SN1/SYS/exe/jvm/hpia64/sapjvm_6.1.046

JDK_HOME_PATHS = JAVA_HOME_4=/usr/sap/SN1/SYS/exe/jvm/hpia64/sapjvm_4.1.020;default=/usr/sap/SN1/SYS/exe/jvm/hpia64/sapjvm_6.1.046

The Build Variant for the 7.00 Track has reference to the JAVA_HOME_4.

We imported the development configurations in the NWDS 7.31 (Track with 7.3 components and custom developments), NWDS 7.0 (Track with 7.0 components and same custom developments). We were able to successfully re-compile the items in the 7.31 and 7.0 DC and deploy to the server directly and the applications have started work in Portal.

Check In of activity is successful in 7.31 and 7.0. But, the activation fails in both the tracks in respective NWDS. When I looked at the CBS Log following the is the information we have -

Bunch of Errors like -

Synchronize metadata for [merck.com/comet/externaljars] started at 2013-03-06 16:34:21.079 GMT

                Verification of DL [ws/ZEPUM73/com.merck_ZEP_UME/dev/active/] finished at 2013-03-06 16:34:21.141 GMT and took 19 ms

                    Verification of cache FAILED due to the following reasons:

                    Cache inconsistency detected: comparison of cache items on the paths:

                        [/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.C/2728/DCs/merck.com/comet/externaljars/_comp/.dcdef]

                        [ws/ZEPUM73/com.merck_ZEP_UME/dev/active/DCs/merck.com/comet/externaljars/_comp/.dcdef]

                    on verification level 2 FAILED:

                    Difference in attribute 'Timestamp' [Mon Mar 04 15:53:41 EST 2013][Mon Mar 04 15:53:42 EST 2013]

and the final build log error is for Java 6 and Java 4 also similar error -

Starting CBS build controller process with JDK '/usr/sap/SN1/SYS/exe/jvm/hpia64/sapjvm_6.1.046'

                Build failed! Unknown error

            Change request state from PROCESSING to FAILED

            Error! The following problem(s) occurred  during request processing:

            Error! The following error occurred during request processing: An I/O error occurred on attempt to start an external process to perform the build. The arguments used the start the process are as follows:

/usr/sap/SN1/SYS/exe/jvm/hpia64/sapjvm_6.1.046/bin/java -Xmx1000M -cp /usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/logging.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~arc~provider_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~arc~provider_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~build~buildwrapper_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~build~buildwrapper_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~build~dcmanager_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~build~dcmanager_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~build~pluginhandler_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~build~pluginhandler_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~build~utility_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~build~utility_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~build~wrapper_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~build~wrapper_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~cbs~buildcontroller_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~cbs~buildcontroller_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~cbs~client_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~cbs~client_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~cbs~common_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~cbs~common_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~complib_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~complib_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~devconflib_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~devconflib_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~dtrclient~deltav~plb_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~dtrclient~deltav~plb_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~dtrclient~protocol~plb_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~dtrclient~protocol~plb_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~dtrclient~vfs_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~dtrclient~vfs_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~util_api.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/tc~di~util_core.jar:/usr/sap/SN1/J03/j2ee/cluster/server0/temp/CBS/34891150/bb/.B/38892/DCs/sap.com/tc/bi/buildtool/_comp/gen/default/public/def/buildtool/ume.jar: com.sap.tc.buildcontroller.CBSBuildController

Error is: Cannot run /usr/sap/SN1/SYS/exe/jvm/hpia64/sapjvm_6.1.046/bin/java - exec failed (ENOENT).

        REQUEST PROCESSING finished at 2013-03-06 16:34:53.711 GMT and took 32 s 727 ms

We are kind of struck at this point now from both the Tracks. Has anyone faced this issues?

Thanks,

Nagarajan.

[Former Member]

Our Bad...JDK Path was incorrect. We fixed the paths and the activities were activated like charm !!!

Thanks.

[former_member196418]

Hi Nagarajan,

In what way was your JDK path incorrect? I am experiencing the same problem and my path is configured very similar to yours (the path to the sapjvm_6.1.018 in my case). In your case was it merely a typo or something else?

Thanks,

Bert

[Former Member]

Hi Bert,

The path that we provided did not have the Java Home. We had to fix that. Hope that helps !!!

Thanks,

Nagarajan

[Former Member]

Hi Nagaraj,

We are facing the same issue in configuring the build path for JVM 4  and JVM 6. Please provide your exact custom value of JDK_HOME_PATH. and the build variant value which you had set for 7.00 tracks.

Thanks,

Gomahti

[Former Member]

Hi Gomathi,

Here is the below we used in the CBS Java System properties in nwa.

JAVA_HOME_4=/sapmnt/<instancename>/exe/jvm/hpia64/sapjvm_4.1.020/sapjvm_4;default=/usr/sap/<instancename>/SYS/exe/jvm/hpia64/sapjvm_6.1.049/sapjvm_6

In the build variant of 7.0 tracks we gave the property -

Property Name - com.sap.jdk.home_path_key

Property Value - JAVA_HOME_4

Hope that helps !!!

- Nagaraj

[Former Member]

Thanks for your clarification Nagaraj. That helps.

We are facing issues while installing both JVM 4 and JVM 6 in the same server. JVM 6 is getting downgraded while installing JVM 4.

Do you have any idea on installation steps for JVM 4? Is there anythig we need to take care while installing JVM?

Thanks,

Gomathi

[Former Member]

Are you installing the Java on the same path? Try installing Java in different paths of the server.

- Nagaraj.

[Former Member]

Yes Nagaraj.  We tried installing JVM in different paths and it did not work.

Basis have just unzippped JVM 4 in location  .. /usr/sap/<instance>/SYS/exe/jvm/linuxx86_64/sapjvm_4.1.001/sapjvm_4 and JVM 6 is available in /usr/sap/DD0/J00/exe/sapjvm_6.

Will it work if JVM 4 is unzipped and placed in a different path in server and JVM 6 is installed in another path ?

Thanks,

Gomathi

[Former Member]

Hi Nagaraj,

Please clarify if you had installed JVM 4 on the server or just untarred the JVM 4 package in a different path. Were you able to compile the old 7.0 tracks with JVM 4 ?

Thanks,

Gomathi

[ErvinSzolke]

Hi,

you can check this thread too:

How to deal with JDK versions

http://scn.sap.com/thread/2079515

Cheers,

Ervin

[Stefan-EA]

If you are only upgrading the NWDI from NetWeaver 7.0 to Netweaver 7.31, you can keep your existing tracks. Since NetWeaver 7.31 uses Java 6, a build variant will need to be added to your 7.0.x tracks  in order for the CBS to build your DCs with Java 1.4.2.

In the CBS Service Properties, you will need to configure the BUILD_TOOL_JDK_HOME and JDK_HOME_PATHS properties to point to the JDKs that you are using. Create a JDK_HOME_PATHS custom value called JDK1.4.2_HOME that points to the Java 1.4.2 JDK.

In all your 7.0.x tracks add the build variant "com.sap.jdk.home_path_key" with the value "JDK1.4.2_HOME".