Hi everyone,
I have a v11 technical question related to the application (gateway) server... The server configuration v11 training emphasized creating separate web sites for each API, thus requiring multiple IP addresses and SSL certificates. In our current gateway server, we use a single web site with each API instance running as a virtual directory within that site. So, we have urls like:
This allows us to use a single IP address and single SSL certificate, which simplifies administration. We can specify separate application pools per virtual directory, so I see nothing in IIS that would technically prohibit this.
Is there any reason why we should not continue this approach? Can we run both REST and SOAP APIs in one web site, as long as each virtual directory is configured with the appropriate application pool? Are there any downsides to taking that approach that perhaps I'm not considering?
Thanks!David
We were considering that but then decided against it because of future server changes. We will be moving the SOAP API server onto a server in our DMZ and keeping the REST API on a seperate server within our internal network. This works for us because for the foreseeable future we won't be using REST for our website.