[Alexei Balaganski]

Is it just me being too dumb to figure it out or is it not possible to deploy a web project to more than one server of the same kind?

For example, I have one tomcat 5 installation on my workstation, which I use for debugging, and another one on the test machine, which is used by testers. Unfortunately, it seems to be impossible to deploy my application on both machines through the Project Deployments interface.
At the moment I just use an ant script for deployment, so it’s not a big problem for me…
But I fail to understand the concept behind this deployment manager. It seems that it can only be used with application server connectors for debugging applications inside the IDE, but that’s not what I call “deployment” 🙂

[Scott Anderson]

Is it just me being too dumb to figure it out or is it not possible to deploy a web project to more than one server of the same kind?

You’re not being dumb. You can currently only deploy to one server of a particular kind and major version number at a time. We’ll be adding an export capability in the future to facilitate creating archives for installation on external servers.

For example, I have one tomcat 5 installation on my workstation, which I use for debugging, and another one on the test machine, which is used by testers. Unfortunately, it seems to be impossible to deploy my application on both machines through the Project Deployments interface.

Interesting. This particular product function may be an outgrowth of our consulting practice. We always recommend that clients completely seperate development from QA, which means that all QA builds should be pulled from the source repository, compiled, packaged, and deployed using all the same techniques as would be used for the final production release.

It seems that it can only be used with application server connectors for debugging applications inside the IDE, but that’s not what I call “deployment” 🙂

Actually, it is indeed deployment, but it’s not QA or production deployment. It’s deployment on one or more servers, simultaneously, in either exploded or packaged form, so that developers can create, debug, and test their applications during the development phase. It really isn’t intended to be a QA or production deployer since those things are typically a much more tightly controlled, audited, and regimented process that is company-specific.

All that said, if you really want to move your builds to QA directly, the current workaround (until we get export enabled) is to simply deploy to your local server as an archive and then copy it to whatever other servers you’d like. 🙂

–Scott
MyEclipse Support

[Alexei Balaganski]

Thank you for your detailed reply. You are right, of course: separate build and deployment is the right way and is, in fact, the way I’m doing it now with help of an ant script.
But I was thinking about something like “click one button and have your application deployed on a remote server”. Sometimes that would be really convenient 🙂

[Scott Anderson]

But I was thinking about something like “click one button and have your application deployed on a remote server”. Sometimes that would be really convenient 🙂

I think we’re on the same page there. We call it “Export”, but who’s to say you can’t “export” directly into an external server’s deployment directory. 😉

–Scott
MyEclipse Support

[Author]

Posts