Pros and cons of installing a local J2EE server

[Former Member]

Hi,

We are about to start developing portal applications with Web Dynpro and will use NWDI (DTR/CBS/CMS). I would like to know what SAP recommends for team development, each developer installs a local J2EE server or they all deploy and test on a central server?

From my past experiences, using only one central server can cause problems with debugging, deployment and collisions of a DC tested simultanously by two developers. Running a local server can solve these problems but this could be costly; first because PCs often don't have enough CPU/RAM to run it, and second to support all these complex installations.

I have read Benny's two blogs and some SAP documentation but it is still not clear to me which option is best. If you have lived good or bad experiences with one or the other please let me know!

Thanks,

Martin

[Former Member · Accepted solution]

Hi Martin,

It seems you already have gathered a lot of information. If you can affort it, go for the local server for every developer. But that is not always the situation. So ...

My experience has taught me that one central server is workable when you have a few developers (1 - 5) that are all in the same location. Then they do not really hinder eachother and if something goes wrong they can consult eachother.

If you have more developers on different locations a local server for each developer is feasible.

Regards,

Christophe

[Former Member]

If you have seen the SAP paper on this that explains the option that should answer your question - How To ...Development Scenarios in NWDI.

Here we have multi clients and are going to try have virtual clones

[Former Member]

Hi Graham,

I haven't read this guide, actually I couldn't find it anywhere. If it's available on the web could you please send me the link to it, or if you only have a local copy send it to me by email?

Thanks,

Martin

[Former Member]

I would strongly suggest you avoid having a single runtime environment for multiple developers. The nature of Java development makes working in a runtime environment such as this very difficult. It's far too easy to have multiple developers working on the same component making changes that result in different versions of the same component getting deployed to the same runtime environment. Unless communication is very good, you're developers will end up clobbering each others changes. Obviously not good, since the developers will spend time trying to debug problems which really don't exist!

At the other end of the spectrum, each developer can have their own Java stack running locally on their desktop PC. This was the solution that we first tested out, but due to the amount of virus scanning and the overall 'weight' of the other software tools on our desktop PC's, this didn't work too well - performance wasn't all that good. It was also too easy for the developer to clobber their own environment by accidentally removing files, or by making changes to the configuration that would render their engine unusable.

What we opted for was something in the middle: a dedicated multi-cpu system with lots of RAM that runs multiple J2EE instances, each of which is assigned to a single developer. What you get from this sort of configuration is this: only a single operating system to patch when you are required to do upgrades; a controlled environment where the developer doesn't have file system access to the system (which they don't need anyways); if you're lucky, basis support to perform installation and patching duties.

We've been using this environment for about a year now, and it works well. I have full access to the J2EE container via the Visual Admin, and since the dev instances are configured as single server debuggable instances, I can restart the server via the Dev Studio with just two clicks.

Hope that gives you an idea of another possible config.

[Former Member]

Hi Ken,

This seems to be an interesting option. Could you please give a little more details about the system you use to run the multiple J2EE instances (OS, RAM, CPU, ...)? How many developers this central server can support, and how much resources a developer typically needs?

Thanks,

Martin

[Jordan_Stanchev]

Hello,

actually the development scenarios and how to set up nwdi in the different development scenarios are part of the sap library documentation.

The scenario descriptions are here:

http://help.sap.com/saphelp_nw2004s/helpdata/en/62/1f5a42672ee054e10000000a155106/frameset.htm

The tutorials for setting up the nwdi are here: http://help.sap.com/saphelp_nw2004s/helpdata/en/88/cb0b405bacdd5fe10000000a155106/frameset.htm

See also the SAP note 737368 for recomendations on your question.

Regards, Jordan

Message was edited by:

Jordan Stanchev

[Former Member]

For those interested I found the guide <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4093a091-ed97-2910-eb94-ca5c2c87513d">How To… Development Landscape Scenarios with NWDI</a> that Graham is referring to. It addresses the question I asked.

Martin

[Jordan_Stanchev]

Hello,

in my reply I forgot to add this interesting <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/44/355274ba830a67e10000000a422035/frameset.htm">link</a>.

Jordan