Virtual host collection
To have a single host machine resemble multiple host machines, go to..
console > Environment > Virtual hosts > virtual_host > Host Aliases
Each virtual host has a logical name and one or more DNS aliases consisting of a host name and a port number. For example...
Environment > Virtual Hosts > default_host > Host Aliases
Host Name Port * 80 myhost.myco.com 40016 When a servlet request is made, the server name and port number in the URL are compared to a list of all known aliases. A match serves up the application running on that host/port. No match returns an error to the browser.
An application server profile provides a default virtual host with some common aliases, such as...
- IP address
- DNS short host name
- DNS fully qualified host name
The host alias comprises the first part of the path for accessing a resource such as a servlet. For example, the host alias is myhost:80 for the requrest...
http://localhost:80/myServlet
Virtual hosts isolate and independently manage multiple sets of resources on the same physical machine. Resources associated with one virtual host cannot share data with resources associated with another virtual host, even if the virtual hosts share the same physical machine. A virtual host is not associated with a particular profile or node (machine), but is associated with a particular server instead. It is a configuration, rather than a "live object." We can create a virtual host, but we cannot start or stop it. For many users, creating virtual hosts is unnecessary because the default_host provided is sufficient.
Virtual hosts route applications/module requests to a particular host/port. The default virtual host is named default_host.
Incoming requests should match only one virtual host. For example, do not have both *:80 and myhost:80 in the same host alias list.
Adding the host name and IP address of the localhost machine (*:80) to the alias table lets a remote user access the console.
Each HTTP transport channel and HTTP transport should have a virtual host alias corresponding to their port. There is...
- One of each on each web container
- One web container on each application server
Create a new virtual host in the following cases:
- Configurating a Web Application Bridge
- Multiple appservers sharing the same virtual host.
Edit a virtual host in the following cases:
- We have an internal HTTP transport with a port other than the default of 9080.
- We use a web server listening on a port not already specified in the virtual host aliases.
Subtopics