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.

Before you begin

You can map a virtual host to a web module during or after application installation using the console. This topic 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. You can install a web module on any defined virtual host. To view information on previously defined virtual hosts, click 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.

About this task

During application installation, a virtual host other than the one you want mapped to your 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
9080
An internal port
9443
An external, secure port

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.

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

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.

Procedure

  1. Click Applications > Application Types > WebSphere enterprise applications > application_name > Virtual hosts in the console navigation tree.
    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 for the web modules.
    2. From the Virtual host drop-down list, select the desired virtual host. If you selected more than one web module in step 3.a.:
      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 stand-alone web module is restarted so the changes take effect.

What to do next

After mapping virtual hosts, do the following:

  1. 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.
  2. Save changes to your administrative configuration.