Defining the bindings in the target web site
When using multiple websites IIS, the administrator of IIS should explicitly define the bindings in the target web site to ensure that the installation serves the requests that target it.
When an IIS has multiple websites it is not clear which website should serve the incoming request which can make the Content Manager installation unstable. On a IIS server with multiple web sites, there has to be mechanism that guides IIS to the correct web site. That mechanism is known as binding configuration. The binding works as a key in a Dictionary of WebSites. So simply, IIS analyzes the request, figures out the key and then goes to the dictionary to find the proper WebSite.
Assume the following values for Content Manager's baseurl and localservicehostname; that is, all requests that have the following host names that must be served by this web site:
- localhostname: example
- hostname: example.com
- http-hostname
- https-hostname
- http-localhostname
- https-localhostname
- http://example/ISHWS/WCF/API/Application.svc
- https://example/ISHWS/WCF/API/Application.svc
- http://example.com/ISHWS/WCF/API/Application.svc
- https://example.com/ISHWS/WCF/API/Application.svc
- https://example.com/ISHCM/
Based on the above examples, to described the possible schema/hostname combinations for Content Manager, the IIS administrator needs to explicitly define bindings for the following combinations:
- http
Example: example.com
- http
Example: example
- https
Example: example.com
- https
Example: example
Configuring the http bindings can be done from the user interface.
Configuring the https bindings must be done by executing a command, such as:
%systemroot%\system32\inetsrv\APPCMD set site [WebSiteName]/bindings:https/*:443:[hostname]
Where you must replace the references to [WebSiteName] and [hostname] appropriately for your configuration and site. There are alternatives that are documented in the help of the commands.
The RequireSSL on IIS SSL Settings forbids any request with the http schema. Based on the above, it is implicitly required that the website cannot have the RequireSSL set to true in the SSL Settings.
The same requirement for RequireSSL on SSL Settings is applied for the infosharewswebappname defined in the input parameters.