Roy,

The WO deployment architecture is such that if you have N web servers and M app servers behind them, a request can come into any of the front-side web servers and it will automatically be routed to the correct app server behind the scenes.

There's nothing sacred about putting files into the location /Library/ WebObjects/Applications. In fact, what you can do is set up a static automount (AFP or NFS) from a head node server that holds all of the files. You can then put the .woa in there and all of the app servers and instances will pick it up automatically. Also note that you don't need a separate .woa for each instance -- all of the instances on a particular machine can execute from the same .woa.


--Paul


Paul Suh http://www.ps-enable.com/
[EMAIL PROTECTED]                           (301) 643-1516



On Apr 24, 2006, at 3:06 PM, webobjects-deploy- [EMAIL PROTECTED] wrote:

Date: Mon, 24 Apr 2006 11:39:04 -0700
From: "Papai Roy" <[EMAIL PROTECTED]>
Subject: Deploying in multiple App and WebServers
To: [email protected]
Message-ID:
        <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1

Hi,
Currently we support a pretty huge marketing website with hitcounts
touching 400-500K sometime. This is totally a WO based application
hosted on OSX servers. To support this we are planning to have an
architecture where 1 webserver will have n appservers under it. And we
are planning to have n=1 for now. But with the number of appservers
growing with time we have a problem of deploying the application in
the appservers simply because of its number.
I would like to know if anybody use a automated deployment script or
any idea how to reduce the effort of moving the application binary to
different appservers?

Any idea is most welcome.

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to