Hi Steve, We are using WebObjects in production environment on AWS EC2 instances and we finished by creating an Elastic LoadBalancer which redirects requests on as many servers you wish. So in principle you create one master instance with Apache+mod_WebObejcts+wotaskd+womonitor, then you create a snapshot of this instance as a model. You can then add as many server instances as you wish by restoring your snapshot and you simply add all your new servers to the loadbalancer. In that way the front-end URL doesn't change and you can handle traffic load very easily.
Hope this helps, Josef Le 24 janvier 2018 à 19:13:27, Steve Peery (spe...@me.com) a écrit: Hi List, All of my WO applications are now happily running on AWS. I work in education so application use varies dramatically during the year with predictable peaks at the end of each term and almost no use during the summer. I currently use a standard deployment with Monitor and WOTaskd all running on one server instance. I am trying to determine the best, most cost effective way to deal with use fluctuations. The obvious solution is to launch additional server instances, but in my past experiences with multi server deployments, Monitor needs to be reconfigured when servers come and go. Any suggestions about the best way to deal with this? Thank you in advance, Steve _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/josef.vanek%40intellicore.net This email sent to josef.va...@intellicore.net
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
