About creating additional portals

When you add portals, you have these options:

• To use the same host name and port number combination, you must specify a unique portal site name for each portal you add. This is the recommended option. For example, for the existing website https://www.acme.com, you could add testportal as the portal site. The URL would be displayed as https://www.acme.com/testportal.
• Use a different port number for each portal you add. The port number is specified in the Advanced Options section of the New Portal form. This is not recommended for production sites because the standard numbers are 80 for HTTP and 443 for HTTPS, and they do not have to be entered by a user. If non-standard ports are specified, users would need to know the non-standard numbers in order to enter the URL. Also, you would need to open the non-standard ports through any firewalls that are in place and make sure there are no port conflicts with other applications on the farm servers.
• In the Farm Manager, add a separate host name for each portal you plan to create.

For IIS bindings, IPF uses the host name/port and does not use specific IP address bindings. With IIS 8.0, HTTPS allows bindings to use the host name. So, for example, you can use *.acme.com and *.acme2.com at the same time. This shows sample portal URLs and whether they are valid:

• https://kfkdkdkf42.acme.com attached to *.acme.com is valid
• https://foo.acme2.com attached to *.acme2.com is valid
• https://acme.com attached to *.acme.com is invalid
• https://subtest.test.acme.com attached to *.acme.com is invalid