Virtual hosts settings
Specify virtual hosts for web modules contained in the application. Web modules can be installed on the same virtual host or dispersed among several virtual hosts.
From the admin console, click...
Applications > Application Types > WebSphere enterprise applications > application_name > Virtual hosts
This page is the same as the Map virtual hosts for web modules page on the application installation and update wizards.
On this page, each web module must map to a previously defined virtual host, identified under Virtual host. We can see information on previously defined virtual hosts by clicking Environment > Virtual hosts in the administrative console. Virtual hosts allow us to associate a unique port with a module or application. The aliases of a virtual host identify the port numbers defined for that virtual host. A port number specified in a virtual host alias is used in the URL used to access artifacts such as servlets and JavaServer Pages (JSP) files in a web module. For example, the alias myhost:8080 is the host_name:port_number portion of the URL http://myhost:8080/servlet/snoop.
The default virtual host setting usually is default_host, which provides several port numbers through its aliases:
- 80
- An internal, insecure port used when no port number is specified
- 9080
- An internal port
- 9443
- An external, secure port
Unless we want to isolate the web module from other modules or resources on the same node (physical machine), default_host is a suitable virtual host for our web module.
In addition to default_host, WAS v9 provides admin_host, which is the virtual host for the administrative console system application. admin_host is on port 9060. Its secure port is 9043. Do not select admin_host unless the web module relates to system administration.
To change a mapping:
- In the list of mappings, select the Select check box for each web module that we want mapped to a particular virtual host.
- From the Virtual host drop-down list, select the desired virtual host. If we selected more than one virtual host in step 1:
- Expand Apply Multiple Mappings.
- Select the desired virtual host from the Virtual Host drop-down list.
- Click Apply.
- Click OK.
If an application is running, changing an application setting causes the application to restart. On stand-alone servers, the application restarts after we save the change. On multiple-server products, the application restarts after we save the change and files synchronize on the node where the application is installed. To control when synchronization occurs on multiple-server products, deselect Synchronize changes with nodes on the Console preferences page.
Web module
Name of a web module in the application that we are installing or that we are viewing after installation.
Virtual host
Name of the virtual host to which the Web module is currently mapped.
Expanding the drop-down list displays a list of previously defined virtual hosts. To change a mapping, select a different virtual host from the list.
Do not specify the same virtual host for different web modules that have the same context root and are deployed on targets belonging to the same node even if the web modules are contained in different applications. Specifying the same virtual host causes a validation error.
Related:
Virtual hosts Mapping virtual hosts for web modules Configure enterprise application files Enterprise application settings