03-22-2018, 05:39 PM
I agree I may be making a strange app. It is a program that will allow university core facilities to manage their core facility. It will have a web front end using IW and the core facility will use it as a portal for their clients.
One of the requirements is to make the installation as simple as possible. The core facility should be able to simply install my software on a server and have it running. Several services need to run on the same computer. (web front end, REST services etc)
If the core facility has to deal with the the university IT staff to do anything sophisticated like: a) update and maintain their DNS to allow multiple IP addresses for the same computer, b) open multiple ports in their internal network for the same computer (with the proxy and firewall issues you allude to above), install and configure IIS etc it will be a huge impediment to uptake. University IT staff is notoriously slow, and one of the advantages I am giving them is that they can have a portal that they do not need to involve IT, or the university website people, to update.
I am presuming that in some way, a webserver is forwarding web requests to the IW server controller. Those requests are coming from IIS (for ISAPI) or from the INDY webserver (for standalone or windows service). I will see if I can figure out how to plugin that into one of the tools that also does direct HTTP.Sys connection, like TMS Sparkle or Synopse.
The only thing I can rely on is that usually (but not even always) port 80 is open in their network and that is the only thing I can use without a hassle.
One of the requirements is to make the installation as simple as possible. The core facility should be able to simply install my software on a server and have it running. Several services need to run on the same computer. (web front end, REST services etc)
If the core facility has to deal with the the university IT staff to do anything sophisticated like: a) update and maintain their DNS to allow multiple IP addresses for the same computer, b) open multiple ports in their internal network for the same computer (with the proxy and firewall issues you allude to above), install and configure IIS etc it will be a huge impediment to uptake. University IT staff is notoriously slow, and one of the advantages I am giving them is that they can have a portal that they do not need to involve IT, or the university website people, to update.
I am presuming that in some way, a webserver is forwarding web requests to the IW server controller. Those requests are coming from IIS (for ISAPI) or from the INDY webserver (for standalone or windows service). I will see if I can figure out how to plugin that into one of the tools that also does direct HTTP.Sys connection, like TMS Sparkle or Synopse.
The only thing I can rely on is that usually (but not even always) port 80 is open in their network and that is the only thing I can use without a hassle.