Virtual hosts settings
To 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.
To view this admin console panel, click Applications > Application Types > WebSphere enterprise apps > application_name > Virtual hosts. This panel is the same as the Map virtual hosts for Web modules panel on the application installation and update wizards.
On this panel, 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 admin console. Virtual hosts enable you 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 JSPs 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
- 9082
- An internal port
- 9443
- An external, secure port
Unless you 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 the Web module.
In addition to default_host, WAS provides admin_host, which is the virtual host for the admin 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 beside each Web module that you 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 you save the change. On multiple-server products, the application restarts after you 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 you 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 concepts
Virtual hosts
Related tasks
Mapping virtual hosts for Web modules
Set enterprise application files
Related
Administrative console buttons
Enterprise application settings