Mapping virtual hosts for Web modules

A virtual host must be mapped to each Web module of a deployed application. Web modules can be installed on the same virtual host or dispersed among several virtual hosts.

We can map a virtual host to a Web module during or after application installation using the console. This article assumes that the Web module is already installed on a server and that you want to change the mappings.

Before you change a mapping, check the virtual hosts definitions. We can install a Web module on any defined virtual host. To view information on previously defined virtual hosts, click 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.

During application installation, a virtual host other than the one you want mapped to the Web module might have been specified.

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.

Use the Virtual hosts page of the admin console to view and change mappings. This page is displayed during application installation using the console and, after the application is installed, can be accessed from the settings page for an enterprise application.

On the Virtual hosts page, specify a virtual host for each Web module. Web modules of an application can be installed on the same virtual host or on different virtual hosts.

 

1. Click Applications > Application Types > WebSphere enterprise apps > application_name > Virtual hosts The Virtual hosts page is displayed.

2. Examine the list of mappings. Ensure that each Web module entry has the desired virtual host mapped to it, identified under Virtual host.

3. Change the mappings as needed.

   1. Select each Web module that you want mapped to a particular virtual host. In the list of mappings, place a check mark in the Select check boxes beside the Web modules.

   2. From the Virtual host drop-down list, select the desired virtual host. If we selected more than one virtual host in step 1:

      1. Expand Apply Multiple Mappings.

      2. Select the desired virtual host from the Virtual host drop-down list.

      3. Click Apply.

4. Repeat steps 2 and 3 until a desired virtual host is mapped to each Web module.

5. Click OK.

 

Results

The application or Web module configurations are changed. The application or standalone Web module is restarted so the changes take effect.

 

Next steps

After mapping virtual hosts, do the following:

1. If the application or module is deployed on a cluster and we have no more configuration changes to make, click Rollout Update on the Enterprise applications page to propagate the changed configuration on all cluster members of the cluster on which the application or module is deployed. Rollout Update sequentially updates the configuration on the nodes that contain cluster members.

2. Regenerate the plug-in configuration file.

   1. Click Servers > Server Types > Web servers.

   2. Select the Web server for which you want to generate a plug-in.

   3. Click Generate Plug-in.

3. Save changes to the admin configuration.

   In multiple-server products, the application binaries are transferred to nodes when the configuration changes on the dmgr synchronize with configurations for individual nodes on which the application will run.

Virtual hosts settings

 

Related concepts

Virtual hosts

 

Related tasks

Set enterprise application files