Team Deployment and Development

[Former Member]

Hi everybody,

we are a team of about 8 developers and we are working together on the project, which is an JEE Application (ear).

We use forge.sap.corp for SCM. Everybody checked out the svn-projects (web, ejb, ear-app, dictionary) as SAP-Development Components using the same local names (I dont know whether this is important).

Now, each of us is developing a component on his own. We made packages inside the EJB Module for each component. Everytime one of us wants to test something, he deploys the whole EAR on the server. This process takes about 3 Minutes or so.

Upon each deployment, the whole application is replaced, which obviously removes the previous deploy of another developer.

Also, if one sets the server to debug mode, for the next deployment, we have to switch back to standard mode, deploy, and set to debug again, which takes approx. 6 Minutes...

-

---

So I have a couple of questions regarding the improvement of out development process:

What is the best practice for our component architecture? Is it okay, to use the same EJB-Module together or should we make an EJB Module for each of us?

How can we change our settings, so that each developer has his own application on the server, to avoid application replacement on the server?

How can we configure the URL of these applications ("Pretty URLs")?

How can we configure the Server to stay in debug mode during the whole process (avoid switch-back before deploy).

What is the best practice for testing our EJBs? We are currently building JSPs, which is a little clumsy.

Thanks in advance!

[Former Member]

"svn-projects"? Don' t you use the NWDI?

"each developer has his own application on the server" The Developer Workplace with integrated J2EE-Engine would serve as individual testing runtime.

"stay in debug mode during the whole process" See above!

"testing our EJBs" In case you need UIs for testing, build Web Dynpros - you get an I/O-screen with a couple of clicks.

Regards,

Thomas

[Former Member]

Hi Thomas,

thanks for you reply. I'm one of the group of 8.

"The Developer Workplace with integrated J2EE-Engine would serve as individual testing runtime." -

What exactly do you mean by Developer Workplace? So far all of us have installed the "SAP NetWeaver 7.1 Composition Environment SP06 PAT0003" which does not seem to contain the Application Server (Installation filesize is roughly ~100MB). After installing all the plugins from the Eclipse(NWDS) Update Manager the installation folder's size is about 900MB, but I can't find anything relating to the Application Server there.

I guess we have to get the AS separately? If so, where? Via the Software Corner?

Thanks you, kind regards

Joerg

[Former Member]

Here' s an [Install Guide|http://help.sap.com/bp_epv170/EP_US/Documentation/How-to/Installation/Install_Developer_Workplace%20(SR1).pdf] for Developer Workplace, but it unfortunatly won' t help much as it refers to NW7.0, not CE.

I' m not quite sure if there already exists a version for CE or if there will ever be one. The good thing about it is that with Dev. Workplace you get an AS Java for your unit tests on your own.

Please ask Basis about this.

Regards,

Thomas

[Former Member]

Hi,

alright I got an Java AS (7.1 CE, Trial Version) installed and running

Is it possible to use a remote Database for the deployment of the J2EE application? We all want to use the same (already existing) DB. At the moment if I deploy to my local Application Server it's trying to use the local DB (which of course doesnt have the necessary tables and stuff).

Thanks in advance, kind regards

Joerg

[Former Member]

For connecting to a remote DB use SAPs Config Tool as described in [Administration Guide for Java AS|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/806e75a0-0e01-0010-2587-fc518de8ac1a] under section "Connecting to a Database".

Regards,

Thomas