Simon, If you're looking for an easy way to move applications from one application server to another then I encourage you to look into using Geronimo's plugin feature. To try this out point your browser at the administration console on the target machine and start the plugins portlet. Next click the "Add repository" link, enter http://source-machines-hostname:8080/console-standard/maven-repo/ and then click the "Add repository" button.
Then back on the initial portlet screen select that new entry from the repository list, enter the Geronimo system username and password for the source machine (default is system/manager), and click the "Search for Plugins" button. You should see a list of all the configurations that can be imported from the source machine to the target machine. You can also use Geronimo's command line interface (deploy.sh) to browse and install plugins The advantage of taking this approach is that it allows you to inspect what configurations are already deployed in a server and selectively choose which you want to import. And the import process automatically imports a configuration's dependencies. If this approach proves to be useful to you then we'd like to hear your feedback. Best wishes, Paul On 1/3/07, problems mail <[EMAIL PROTECTED]> wrote:
David, Thanks for the reply, I will study this and see how I can set it up. Here are couple of reasons: i) when a developer has completed the task he currently deploys the application to the server. It is easier to show the changes to the users on the common development box for the work that has been completed instead of having to display from his/her machine. ii) currently our development environment is centralized (a percentage of security reason) + task visibility + user productivity etc. and all the mgmt b*** ****. This is pretty much how things work here, and has to stay that way :(. There was an option to make changes in their development environments and deploy them to a common environment but we currently have this done into staging. The issues that can arise when people deploy into a common server location is very difficult to debug. Also, I was hoping if someone has already taken the pain of setting this up to share his/her information. If I manage to complete this and make the environments, I will certainly publish this over here. -- Regards, Simon On 1/2/07, David Jencks <[EMAIL PROTECTED]> wrote: > > On Jan 2, 2007, at 10:58 PM, problems mail wrote: > > > Hello, > > > > I would like to setup a development server for multiple developers > > on Geronimo. Is there a development setup for this ? > > > > Using tomcat we would have different ports and separate > > installations of tomcat. > > > > Anyone already setup their development environments ? - Please > > provide details. > > This is possible, but I have to wonder why your developers don't just > run geronimo on their own machines. > > You can change the ports using the config.xml file. > > You can actually share the geronimo repository by starting with a > command line argument > > java -Dorg.apache.geronimo.server.name=myServer -jar bin/server.jar -- > long > > in which case the server specific files will be located in myServer/var > > However you may find that each developer deploying the same app on > their server interferes with the same app deployed by other developers. > > this will require you to change a lot of ports, such as jndi (1099), > remote deploy, possibly the ejb listener, etc etc. > > You can also just start a lot of tomcat instances in one copy of > geronimo -- basically copy the tomcat plan, rename the configuration, > and change all the ports, and deploy it. the app deployment plan can > select the tomcat instance using the <web-container> element (IIRC). > However the apps will all have to have different moduleIds determined > by the plan. > > I hope you have a good reason to try to do this because it is going > to be a substantial amount of nuisance to set up. > > thanks > david jencks > > > > > > -- > > Regards, > > Simon > >
