SAP Netweaver CE 7.1 Ehp1 SP5 & multiple SAP release version support

[Former Member]

Hi,

I've just built and configured the first SAP CE 7.1 Ehp1 (to latest SP 5) with SLD , ESR & NWDI capabilites configured post installation. Based on the documentation I've also setup 2 PC's that are intended to be used by developers in conjunction with the new CE environment to utilize the DTR/CBS capabilities.

We'd like to have this CE server support various developments - ESS/MSS Webdynpro based on ERP 6/ NW 7 Portal, ERP6 Ehp4 based XSS development, PI 7 and a couple of other non-SAP Java based applications that are certified SAP complimentary products. I've been scouring the CE materials and forums looking for confirmation that our new CE 7.1 Ehp1 Environmnet ( with the 2 NWDS NW 7.1 Ehp1 SP 5 version ) can support multiple developements for components that are intended to be deployed on environmnets with differing Java component release and support package levels.

I'm assuming the individual track definitions can accomodate spanning different NW Java releases based on some of the Wiki's etc I've looked at but the more I look into it the more confused I seem to become around how the SAP CE 7.1 Ehp1 server and the NWDS which are the same release levels can support development of NW 7 based Java applications & XSS Webdynpro.

Can anyone shed any light on this or point me to where I can find information that clarifies what the capabilities are for NWDS / CE supporting multiple developments of various Java/Webdynpro projects.

Or - do we need to build separate CE / NWDS environmnets which are aligned to support the individual products being developed, for example would a NW 7 XSS Webdynpro development need to be done on a specific release of CE /NWDS with another CE / NWDS release level being required to perform XSS Webdynpro developments for an ERP 6 Ehp4 based development.

Many thanks,

Brian.

[ErvinSzolke · Accepted solution]

Hi Brian,

I hope this answers your questions. If so, could you please mark the thread as solved?

Thank you!

Best Regards,

Ervin

Edited by: Ervin Szolke on Sep 2, 2010 12:04 PM

[Former Member · Accepted solution]

Ervin,

What about runtime system setup? Since there is no SDM on 7.1+, how do we configure the runtime systems in CMS? I am more interested in NW 7.3, but I think the configuration is similar.

[Former Member · Accepted solution]

Hello Mohammed.

If your Runtime-System is higher than 7.1, you have to choose "Deploy Controller" instead of "SDM".

You have to fill in the following fields:

- Deploy Host => Either the SID or the FQDN (Full qualified domain name) of your Runtime-System

- Deploy Port => If you develop a J2EE-Application, the Deploy-Port is: 5XX04. XX is the instance-number, on which your J2EE is running (you cann see it in your SLD)

- Deploy User + Deploy Passoword => Ask your admin.

Don't set a checkmark on "Integrate runtime system into JSPRM scenario" or "Disable automatoc Deploymnet"

After you have filled all the above-named field, pleas click on "View/Edit Deployment Substitution Parameters". If you can see now, some variables, which where added automatically, you have done everything right:)

Best Regards.

[Former Member]

Hi Ervin,

thankyou. Your replies have cleared everything up for me. Your thoughts have been of great help to me and have saved me a lot of further time trying to find the answers.

I'll mark this thread as closed now.

Regards,

Brian.

[ErvinSzolke]

Hi Brian,

yes. As per the guide above "JDI Software vs. JDI Content", the SP of the NWDS needs to match to the SP of the RunTimeSystem(s) where you intend to deploy, and also as per the same guide, NWDI musn't be lower than your NWDS instance(s).

In your example I'd therefore suggest to have on server side:

- NWDI on 711 SPX

on client side 2 NWDSs for each developer::

  - 700 SP21 (with this 700 SP21 NWDS you can deploy to RTS with version 700 SP21)

  - 711 SPX (with this 711SPX NWDS you can deploy to runtime systems with version 711 SPX)

Best Regards,

Ervin (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home)

Edited by: Ervin Szolke on Sep 2, 2010 11:53 AM

[Former Member]

Hi Ervin,

Thanks again for your swift reply. I think I've got it now regarding the NWDS client. Based on what you've said I think I need to have the developers setup the connections in the NWDS to respective SAP WebAS Java instances that support their development.

For example, a development starting for a XSS development based on NW 7.0 SPS21 Portal could use the SAP NW 7 SPS21 Java Instance of our developemnt XSS portal by defining this connection in the NW 7 SPS21 bversion of NWDS and for another development for a NW 7.11 based application landscape would need another 7.11 NWDS installed on the developer PC where I could then define the WebAS Java connection to use the NW 7.11 development system's Java Instance for that landscape development. This would keep the NWDS release in line with the corresponding Java release & SP levels of the intended development landscape.

Sorry to be asking you so many questions but this is my first technical build of a CE / NWDI infrastructure to support development and the planning guides etc don't really provide enough clarity for me.

Regards,

Brian.

[ErvinSzolke]

Hi Brian,

if you intend to develop for 70X and 71X then I strongly recommend to have two separate NWDS instances on the client side, one for 70X and an other NWDS for 71X. The architecture is slightly different. The problem is that NWDS has also many client tools in order to co-operate with the engine. Just think of dtr/cbs clients, the deployer tool. To mention one example I guess a 700 NWDS is not aware of things like deploy controller for 71X, has only sdm client, etc.

Best Regards,

Ervin (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home)

[Former Member]

Hi Ervin,

many thanks for your reply - this has helped clearup a lot of my confusion. The NWDS version being alligned to the particular development release , 7.0x for NW 7.0x based development & 7.1x for NW 7.1x makes sense now.

The only thing I am still unclear about is that when I was planning the CE 7.1EHp1 server build (where the NWDI, SLD & ESR capabilities are also located) I'm sure the guides specified that my NWDS version needed to match the release of the CE system. The CE system is where our NWDS PC's will use the Java Instance as the PC's only have the Developer Studio installed and not the full-blown workplace with it's own Java Instance.

Have you any thoughts on this as we may need to support 7.0x & 7.1x based developments from the same developer PC's.

Regards,

Brian.

[ErvinSzolke]

Hi,

NWDI is only a framework, it can have any release, and still you'll be able to develop for any releases.

An example, theoretically a 640 NWDI can be used to develop 720 projects (an other question we don't recommend 640 any more as it is pretty old version and has way less features like higher releases).

The relevant questions regarding the development are:

1 what is the version of the track (more precisely what is the version of the dependent software components)

2 what is the version of the runtime system where I deploy to.

Obviously these 2 must be the same release and SP version.

I send you a very good blog which hopefully sheds some light,

JDI Software vs. JDI Content -

and also send you a doc which explains what to do if you want to develop (using a specific NWDI release) for different releases (not to mention follow-up problems like 70X and 71X are using different JDK versions for development. To resolve these problems, see the guide):

How To... Setup an NWDI Track for Composition Environment Developments - https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7014086d-3fd9-2910-80bd-be341781...

Caveat factor: There's no NWDI framework available for 710, only as of 710 EHP1 (i.e. 711), so please do not plan to deploy NWDI framework to 710 as you'll not find the corresponding SCs to it on the service marketplace.

One last remark: yes, it is enough if you have only one NWDI framework installed on your 711 engine on server side (it'll serve your 640/700, 701,710,711, etc. etc. developments) and no it is not enough to have only one NWDS on the client side to serve the development for all releases. For 700 Development you need to use 700 NWDS. For 710 development you need a 710 NWDS. For 720, a 720 one, etc.

I hope this helps!

Regards,

Ervin (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home)

Edited by: Ervin Szolke on Sep 2, 2010 10:42 AM