Hi Rick,

I would like to try and isolate some functions in my platform and generate a new exe for them. I thought to myself, no problem, I will setup two 'sites' in IIS, copy wc.dll and wc.ini to two different folders, map each 'site' to each unique dll, and map each handling mapper to each, and away I go (in file mode to start). One last comment, I created a duplicate copy of the exe and renamed it, thinking that in file mode this should not matter.

Does this sound reasonable so far?

Is this an answer to your question? Running multiple Web Connection Apps on a single server

Thanks Tore - it confirms what I was trying to do to an extent. I should have also said that I'd like to see if i can use ISAPI and .NET on same server with SAME handler mappings for two different sites. I am hoping to use .net on the new isolated site with its own exe. Rick has docs on setting up A or B but not sure about both.

Hopefully Rick fills in the missing parts. The truth is that I have spent the last few weeks reading the Help file (yes, every single subject), and I remembered having read the one I linked to.

Great catch. My scenario will need what you showed me for sure, because I am fairly certain you cannot run both ISAPI and NET on same box with same app. Rick will chime in I hope.

Rick - if you are wondering WHY - the thinking is that my API will run isolated and rarely need updates, whereas my CMS/ecomm is getting updated daily. The API needs to do its thing and be protected from bugs in non related cms mods. While it should run on its own servers, I want it to be able to run a single server for some implementations.

So, I guess you could frame this up as 'Single tenant + multi tenant' on a single instance.

Yes, recent versions of Web Connection make it very easy to run multiple applications side by side. Even separate versions of Web Connection altogether as well.

Older versions - it depends on how the projects were set up. By default everything landed in \wconnect which makes the isolation a lot harder.

If you need to run the same application in multiple virtuals/sites, that can also be done but... you will likely need to create two separate COM servers that you can call.

It's easy enough to do by just subclassing the main COM server into a new class:

DEFINE CLASS MySecondServer As MyFirstServer OLEPBULIC
ENDDEFINE

You then end up with:

• MyFirstServer.MyServer
• MySecondServer.MyServer

as COM objects that can be invoked separately if necessary. This allows you to configure the server slightly differently if you need to.

+++ Rick ---