NWDI - Java 1.4 & Java 1.5 does work :-)

[petr_solberg]

Hi All,

we have NWDI, and it has always worked fine, used for transporting WebDynPro's for Portal applications.

Now in our landscape we have CE and we need to configure tracks for CE,

as lots of people know, CE needs Java 1.5 and normal NWDI Portal applications need Java 1.4

The documented solution for this is to change the CBS config to use Java 1.4 and Java 1.5

We did this, but now, we cannot transport Portal WebDynPro's, we get this error:

Compiling 40 source files to /usr/sap/SID/JCxy/j2ee/cluster/server0/temp/CBS/2b7/.B/108961/t/4F60AFF0849BCE7E989388BC8481DCEF/classes/src.core

[javac] ERROR: /usr/sap/SID/JCxy/j2ee/cluster/server0/temp/CBS/2b7/.B/108961/DCs/sap.com/pcui_gp/xsscfg/_comp/src.core/com/sap/xss/config/pcd/PcdObjectBroker.java:177: as of release 1.5, 'enum' is a keyword, and may not be used as an identifier

[javac] ERROR: (try -source 1.4 or lower to use 'enum' as an identifier)

[javac]

It is showing that NWDI is not supporting the Java 1.4 and Java 1.5 configured in parallel

Unless anybody knows better, it looks like the only solution to support Portal and CE NWDI transports in a SAP landscape will be to have 2 x NWDI's

1 x NWDI configured for Java 1.4 for Portal WebDynPro transports

1 x NWDI configured for Java 1.5 for CE transports

as time goes on it will be interesting to see the experiences of others. We will experiment and see if we can activate NWDI on the CE Dev system and let that be the NWDI server for the CE landscape

Regards,

Petr.

Edited by: Petr Solberg on Jul 14, 2009 12:13 PM - to change the subject heading, it works ! in the next post i give the key

[petr_solberg]

SAP solved it

who's the best, SAP's the best

[petr_solberg]

Hi All,

with great help from SAP we got the answer to this one

If you have one NWDI, and you want to support:

Portal and CRM developments using JDK 1.4

and

CE developments using JDK 1.5

then you need to do this,

in your NWDI,

either, set the build home to JDK 1.4 OR JDK 1.5

make a jdk home variable for JDK 1.4 and 1.5

if you set the build home to JDK 1.4, then in your ce tracks set the build variant to JDK 1.5

if you set the build gome to JDK 1.5 then in your portal and crm tracks set the build variant to JDK 1.4

it works

thanks SAP

Petr.