I'm trying to find a way to host multiple clients' Public Sites on the same Virtual Server. Each would have their own dedicated IP and the Public or WCM would be installed using the Custom installation option. I want to avoid potential version conflict issues as time goes on between each implementation. I was told to perform an initial installation of iMIS which would be used primarily for creating multi instances for each client and provide a means of applying upgrade patches when needed. Has anyone else been successful in running more than one client public site from the same server or is it necessary to dedicate a Virtual Server to a single client?
If the single client per server option is the only means then would be the minimum required drive space and memory requirements for just the Public or WCM setup?
Should be on the right track.
I think what you've been told is pretty good advice. I haven't set up multiple clients on one server, but I have set up test and live sites, and upgraded test without live.
The key is to make sure your first install is *not* a real site, because when you apply a patch or an upgrade, it will only update that one copy. For a single client, I would install the Test or Dev site first, then make the live site a "multi" copy. For a server hosting multiple clients, I would make the first install a generic install, not specific to any client and never served. That way you can copy it and upgrade it whenever needed. (Make a new clean copy of 15.0.1 before upgrading to 15.0.3, then make another clean copy before applying 15.1. Maybe even for every patch level.)
Also be careful with the Workflow services. The multi utility will want to create a new Windows service each time you run it. It's good to have a naming convention so you can keep all the copies straight. The default names aren't very helpful, especially when the Multi utility uses a different pattern than the original install.
-- Bruce