Use this panel to specify virtual hosts for Web modules contained in your application. Web modules can be installed on the same virtual host or dispersed among several virtual hosts.
To view this administrative console panel, click Applications > Enterprise Applications > application_name > Selecting virtual hosts for Web modules - Map virtual hosts for Web modules. 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. You can see information on previously defined virtual hosts by clicking Environment > Virtual Hosts in the administrative 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 that is 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:
Unless you want to isolate your Web module from other modules or resources on the same node (physical machine), default_host is a suitable virtual host for your Web module.
In addition to default_host, the product 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:
Specifies the name of a Web module in the application that you are installing or that you are viewing after installation.
Specifies the 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.