Configuring a new NWDI with replicated DTR

[Soumya]

Hi Everybody...

I am currently working on setting up a NWDI so that development work can begin on it.

We have to move around 6 tracks from old NWDI [7.0] to new one [7.3]. This NWDI has different SLD, DTR, CMS and CBS. My team was supposed to just replicate DTR and start working on developments on the moved / replicated tracks. But after replication [in this thread] when we are connecting via NWDS and trying to "create a project" from a Inactive DC from a track, we are getting errors. We have tried on ESS as well as MSS DCs. We are not able to figure out which steps have we missed or performed wrong which is resulting in error.

Some Errors:

# The method wdGetStaticMetadataCache() is undefined for the type SalarySurveyDataModel Bapiret2.java <SID>_MSSTRK_D~mss~eepro~salarysurveydata~sap.com/gen_wdp/packages/com/sap/xss/hr/eeprofile/salarysurveydata/model line 52

# com.sap.tc cannot be resolved (or is not a valid type) for the argument scope of the method Bapiret2 Bapiret2.java <SID>_MSSTRK_D~mss~eepro~salarysurveydata~sap.com/gen_wdp/packages/com/sap/xss/hr/eeprofile/salarysurveydata/model line 94

# Cannot get build plug-in for DC "sap.com_SAP_MSS_1:sap.com/mss/ecm" in configuration "<SID>_MSSTRK_D" : Component sap.com/tc/bi/bp/webDynpro does not exist on the build server (CBS Server Error: Unknown development component ( internal code: DC_UNKNOWN)) (Component sap.com/tc/bi/bp/webDynpro does not exist on the build server (CBS Server Error: Unknown development component ( internal code: DC_UNKNOWN)))

# failed to resolve reference "sap.com_SAP_MSS_1:sap.com/mss/ecm" for DC "Cannot find compartment of used component: sap.com:com.sap.mw.jco": {2}sap.com/com.sap.mw.jco

# failed to resolve reference "sap.com_SAP_MSS_1:sap.com/mss/ecm" for DC "Cannot find compartment of used component: sap.com:pcui_gp/oadp": {2}sap.com/pcui_gp/oadp

# failed to resolve reference "sap.com_SAP_MSS_1:sap.com/mss/ecm" for DC "Cannot find compartment of used component: sap.com:pcui_gp/xssfpm": {2}sap.com/pcui_gp/xssfpm

Thanks in advance for valueable suggestions

... -.-.

[Soumya]

Hi Ervin,

The parameters have been set and have tried creating projects in NWDS from tracks.

After the BUILD_TOOL_JDK_HOME and JDK_HOME_PATHS have been set, the importing function under Development tab in CMS is working like breeze.

Two issues I have come across while creating projects from inactive DCs in NWDS.

Initially the project creation was failing stating "Cannot find used DCs...". Placing correct .sca files in CMS/Inbox, then importing them in Development tab solved them.

First error is regarding a track with ENGFACADE and SAP_BUILDT as dependencies. While creating a new project out the inactive DCs, it is throwing no errors and log in NWDS 7.3 is showing "Build successful". One of the DC which has 4 jsps is showing a small red cross beside it though not showing build errors. The error is due to not being able to import "com.sapportals...."

Please see the below screenshot.

I found in one article that this is a bug in NWDS 7.3. Is is correct??

Second Error is regarding a MSS track. It was based on MSS 600 with dependencies as per 7.0 requirement. The same tracks was replicated in DTR of 7.3 and have created the track in CMS 7.3 with same track definitions as found on CMS 7.0. While creating projects from inactive DCs, (I am performing the operation of project creation in NWDS 7.0 [Not 7.3] with JDK 1.4.2) two errors appeared: 1> cannot find DC - tc/wd/webdynpro. This I solved by placing SAPJEE_xxxxx.sca in CMS/inbox of 7.3, as found in inbox of 7.0 2> cannot find DC - tc/ddic/ddicruntime. This I solved by placing SAPJTECH_xxxxx.sca in CMS/Inbox of 7.3 as found in inbox of 7.0. Is this approach correct ??

Each time I delete the old configuration and then import freshly from SLD. Now, while creating a project from inactive DC [mss/ecm etc], I am getting an error saying:

/userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: mss/ecm: Build failed for sap.com/mss/ecm(sap.com_SAP_MSS_1) in variant "default": com/sap/tc/buildplugin/DefaultPlugin (Unsupported major.minor version 49.0)

I found out that this may be due to mismatch of JDK of local machine NWDS and CBS build variant. Our operation is to shift tracks from NWDI 7.0 to NWDI 7.3. The applications will be running on 7.0 portals only, hence the ESS/MSS wont be upgraded, as of now and all changes will be done via NWDI 7.3. So please advise how to solve this java mismatch issue.

Thanks,

Soumya

[Soumya]

Any help is appreciated...

[ErvinSzolke]

Hello Soumya,

sorry for the late response, I was not available recently.

The best approach I can suggest is to read this thread very carefully:

How to deal with JDK versions

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

I believe it summarizes everything via examples how to deal with JDK versions.

If you knew this already or read it already then I will ask you to provide couple of screenshots of the jdk settings related to nwdi, but first please let me know if this helps.

Thank you and Best Regards,

Ervin

[Soumya]

Hi Ervin,

The link you have mentioned was helpful, but I had already asked Basis Team to install and configure 3 JDKs as mentioned earlier.

Following are the current configurations of CBS:

Then in the track in CMS I have changed the build variant as per sections 3.2 and 4.4 of the following doc: http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7014086d-3fd9-2910-80bd-be3417810...

After setting the new build variant, should I go for "Initialize" or "Build" in CBS ??

--

Soumya

[ErvinSzolke]

Hi Soumya,

I can see one potential problem. In the screenshots I can see JRE, but JRE is not allowed here, only JDK. Please download a JDK 1.6 and adjust the BUILD_TOOL_JDK_HOME, and notice that the JDK_HOME_PATHS is also affected due to JDK1.6.0_HOME.

Best Regards,

Ervin

[Soumya]

Ok, I will ask for the same.

But we are trying to build the MSS track with JDK 1.4.2 build variant.

When creating any project from the track in NWDS 7.0 we are getting the error : "userOut/Development Component (com.sap.ide.eclipse.component.provider.listener.DevConfListener) [Thread[ModalContext,5,main]] ERROR: mss/ecm: Build failed for sap.com/mss/ecm(sap.com_SAP_MSS_1) in variant "default": com/sap/tc/buildplugin/DefaultPlugin (Unsupported major.minor version 49.0)"

in NWDS itself.

Does the path for JDK1.6 has any effect on track with JDK 1.4. ??

Regards,

Soumya

[ErvinSzolke]

Hi Soumya,

yes, I believe it counts.

Let me add here an older (but very good) description about these parameters:

I hope this helps,

Regards,

Ervin

----

How does CBS handle multiple JDK versions?

CBS uses two service properties to configure JDKs used for the build: BUILD_TOOL_JDK_HOME and JDK_HOME_PATHS. These two settings combined with build options in the development configuration determine which JDK is used when compiling Java sources during a DC build. 

The BUILD_TOOL_JDK_HOME property determines the VM that executes the build environment including Ant. Due to compatibility restraints this VM should be configured to the highest version available or used on the CBS. If you want to use a version 71x and build plugins you must use a JDK5.0 here, for higher releases like 720, 730 use JDK6.0. For older releases (NW04/NW04s) a JDK1.4 is sufficient. (The typical symptom that the build tool JDK should be updated is an error reporting something like "unsupported major.minor version 49.0 ...") 

The JDK_HOME_PATHS property defines a list of key-value pairs where the key is typically something like JDK<version>_HOME and the corresponding value is the path where the JDK is actually installed on the server. There is also the special key default that defines which JDK should be used as default.[1] 

The JDK that is used for the Java compiler is determined using the following logic: 

1. If the build option com.sap.jdk.home_path_key is set to a valid key in JDK_HOME_PATHS then that JDK is used to fork the Java compiler.
   For legacy support the build option ant_jdk_version is checked as fallback and if a valid key in JDK_HOME_PATHS exists with JDK<ant_jdk_version>_HOME then that JDK is used. 
2. If a default JDK is defined in JDK_HOME_PATHS then that JDK is used.

  If the JDK that will be used is different from the BUILD_TOOL_JDK_HOME the Java compiler will automatically be forked as a separate process. To determine if the two JDKs are different the installation paths are compared. 

Example: 

Let's assume the JDK_HOME_PATHS is set to:
JDK1.3.1_HOME=C:\jdk1.3.1_15;JDK1.4.2_HOME=C:\j2sdk1.4.2_09;JDK1.5.0_HOME=F:\jdk1.5.0_06;default=C:\j2sdk1.4.2_09
and BUILD_TOOL_JDK_HOME is set to F:\jdk1.5.0_06 

Some possible scenarios: 

• If the build option com.sap.jdk.home_path_key is not defined the build will be executed on a JDK5.0 VM, but the Java compiler will be forked to C:\j2sdk1.4.2_09 as that is defined as default

• If the build option com.sap.jdk.home_path_key is set to JDK1.4.2_HOME the build will be executed on a JDK5.0 VM, but the Java compiler will be forked to C:\j2sdk1.4.2_09

• If the build option com.sap.jdk.home_path_key is set to JDK1.6.0_HOME the build will fail because no valid local JDK has been defined in JDK_HOME_PATHS for the key JDK1.6.0_HOME

• If the build option com.sap.jdk.home_path_key is set to JDK1.5.0_HOME the build will be executed on a JDK5.0 VM and the Java compiler will be executed within the same VM.

[Soumya]

Hi Ervin,

Sorry for such late update. This is the current configuration after changes. Currently this job has taken backseat due to some other projects getting delayed. Do we need a CBS restart after these changes ??

Thanks,

Soumya

[ErvinSzolke]

Hello Soumya,

yes, it looks better now, and yes, CBS has to be restarted always if you change any parameters on this configuration screen.

Please let me know if you still face problems like "(Unsupported major.minor version 49.0)".

Best Regards,

Ervin

[Soumya]

Hi Everybody,

Can anybody suggest if This might be related to database?? I came across some SAP Notes suggesting Database parameter changes..

Thanks,

... -.-.

[ErvinSzolke]

Hi Soumya,

did you use your 730 NWDS for importing the tracks from the new NWDI? If yes, could you please make an attemp to remove the development configuration and import it again?

Regarding RTSs. There are no mandatory RTSs. All of the 4 systems (dev, cons, test, prod) are optional. Of course if you want to test your stuff centrally then it makes sense to specify at least one RTS else no central deployment will take place.

Best Regards,

Ervin

[ErvinSzolke]

one addition, regarding RTSs I am aware of one restriction only: that it must not be the same system where your NWDI resides. The engine where your NWDI is running cannot be targetet as a runtime system.

[Soumya]

It is a 7.3 NWDS, fresh installation. Installed 3 weeks back. Target NWDI is the only I have ever connected to.

RTSes are on diferent systems than NWDI

One thing I found out in this time that BUILD_TOOL_JDK_HOME and JDK_HOME_Paths have not been defined.

Have asked them to be set as following:

a> Set BUILD_TOOL_JDK_HOME to the <path of JDK1.6>

b> JDK_HOME_PATHS = JDK1.4.2_HOME=<path of jdk142>;JDK1.5.0_HOME=<path of jdk150>;JDK1.6.0_HOME=<path of jdk160>;default=<path of jdk142>

Thanks

[ErvinSzolke]

HI,

ok, the settings looks fine as you described above, but once it is really set by your customer/colleagues, then rather doublecheck it for typos, and correctness.

If the same build error is coming then please trigger an Initialize compartment (you can do it in the CBS webui once selecting the compartment in question) and try again.

Regards,

Ervin

[Soumya]

I came across couple of articles mentioning RTS [Runtime System] needs to be defined for the tracks. Dev and Cons RTS has been defined as I found it is mandatory.

Why is it mandatory ?? Is it Ok that these RTS are not on same SLD as the NWDI ??

After defining RTS, I trying to "Import" the SCAs [Engfacade, SAP_Buildt etc]. It is failing. The log is showing:

20130118074133 Info :Starting Step CBS-make at 2013-01-18 07:41:33.0228 +1:00

20130118074140 Info :wait until CBS queue of buildspace <SID>_PRTLTRK_D is completely processed, before starting the import

20130118074141 Info :CBS queue of buildspace <SID>_PRTLTRK_D is completely processed. Starting the import now.

20130118074229 Info :wait until CBS queue of buildspace <SID>_PRTLTRK_D is completely processed, before asking for build results

20130118074229 Info :waiting for CBS queue activity

20130118074259 Info :build process already running: waiting for another period of 30000 ms

20130118074329 Info :build process already running: waiting for another period of 30000 ms

20130118074359 Info :build process already running: waiting for another period of 30000 ms

20130118074429 Info :build process already running: waiting for another period of 30000 ms

20130118114343 Info :build process already running: waiting for another period of 30000 ms

20130118114413 Info :build process already running: waiting for another period of 30000 ms

20130118114443 Info :no changes on the CBS request queue (<SID>_PRTLTRK_D) after a waiting time of 14430000 ms

20130118114444 Fatal :The request queue is not processed by the CBS during the given time intervall => the import failed because not every request including follow-up requests were processed

20130118114444 Fatal :Please look after the operational status of the CBS.

20130118114444 Info :Step CBS-make ended with result 'fatal error' ,stopping execution at 2013-01-18 11:44:44.0195 +1:00

Why is it failing ??

Please help..

... -.-.