>Like to hear what other alternatives any of you have implemented to make sure >4DRemote as Web server is always operational.
I had once a 24/7 online payment system running for a customer. We had three 4D Server (all windows), each one (potentially) serving directly the web, with attached 4D Clients (all windows) for sending emails, generating PDFs, doing payment transactions etc. They were all behind the firewall. In the DMZ there was a load balancer together with some apache server (with automatic failover), which served static content. All three 4D Server replicated all changes via custom programming in near real time. Two of the 4D Server ran without journal file and without backup, the last one with journal file and backup. Dynamic content was requested from one of the three 4D Servers via reverse proxy. No load balancing here, exactly one of the three was the 'active' Server. Which one of them was configured in the config files of the apache servers. With this setup we could always take one 4D Server down for update or maintenance and have the other one active with the third as fail over. The attached clients were monitored (and automatically restarted if necessary) by 'robot watchdog' from Jens Blomster. HTH Ingo Wolf -- ViELMAC Ingo Wolf Rheinhessenring 53A D 55597 Wöllstein Tel. +49 (0)6703 3070320 Fax +49 (0)6703 3070321 e-mail [email protected] ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
