File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes BEA/Weblogic and the fly likes DEV environment - best practice Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "DEV environment - best practice" Watch "DEV environment - best practice" New topic
Author

DEV environment - best practice

Rama Raghavan
Ranch Hand

Joined: Aug 22, 2001
Posts: 116
Say if there are 10 developers working towards construction of one application..
When setting up weblogic environment (7.0sp1) on unix for development (assume licensing and related costs are taken all care)..here are some q's:
1. Create multiple managed server instances, one per developer (unique ports on the same host), and have each developer deploy a war in respective server instance, OR
2. Create one single managed server and have each developer deploy as multiple apps (dev1.war,..,dev10.war)
And what if this grows from 10 developers to over 20, working on several web apps/components..
Trying to figure out how to manage a development environment effectively and at the same time not step on each other.
thoughts, accusations, do's, don'ts - welcome.
Chris Mathews
Ranch Hand

Joined: Jul 18, 2001
Posts: 2712
I like having individual developers with local development copies of WebLogic running on their workstation. This allows them to become very familiar with WLS and minimizes the impact various development efforts may have on one another.
I than configure a central test server to run complete project builds, preferably in a continous integration fashion. This is usually the machine that QA whacks on (if you have a separate QA division).
What is your preferred setup Aaron?
Aaron Mulder
Author
Ranch Hand

Joined: Feb 25, 2003
Posts: 65
I guess it depends on your licensing setup and hardware configuration. Assuming each developer has a license and a reasonably powerful box with 512MB+, I'd prefer to let each developer run their own WebLogic. That way you're sure you're not interfering with any else if you restart the server, you can take it home with you if you have a laptop, etc. The you can set up one dev instance (for nightly builds/tests or whatever) and/or one test instance (for QA) on the server.
If you only have a license for one box, I'd prefer to set up 10 WebLogics on that box (one per developer), instead of one WebLogic with 10 web apps. It's not unusual to need to restart the server for some reason or other, and you don't want to kill everyone else when you do. However, this box would then need a LOT of RAM. Also, I'm not actually sure whether one license is enough to let you run 10 parallel servers on the box, or whether you'd need 10 licenses even for the one box.


<a href="http://www.javaranch.com/bookpromo.jsp" target="_blank" rel="nofollow">WebLogic Book Giveaway</a> 2/25-2/27
Rama Raghavan
Ranch Hand

Joined: Aug 22, 2001
Posts: 116
Assuming each developer has a license and a reasonably powerful box with 512MB+

How about if the developers are on a UNIX box ? (Assume enterprise license and/or other full licensing requirements satisfied)
Aaron Mulder
Author
Ranch Hand

Joined: Feb 25, 2003
Posts: 65
Well, I do all my developmnt on a Linux PC. That works great. Or are you saying, all developers work on a single big UNIX box? That's the case of installing 10 WebLogics on one server, and you need much more than 512MB in that case. It would be my first choice to have each developer use their own box.
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1859
Hi
As stated in many places here, as far as our development have two environments
One the local environment (Windows 2000)
Second the dev environment (Unix box)
We do our code change and test it in the local environment. Then we check in the code and label it. Notes are circulated as to which changes are to be part of the next dev environment. These particular files are labeled so that they become a part of the dev build.
The new dev build is started and tested by testers.
[ February 28, 2003: Message edited by: Rahul Mahindrakar ]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: DEV environment - best practice