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 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
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:
- If the application or module is deployed on a cluster and you 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.
- Regenerate the plug-in configuration file.
- Click .
- Select the web server for which you want to generate a plug-in.
- Click Generate Plug-in.
- Save changes to your administrative configuration.
In multiple-server products, the application binaries are transferred to nodes when the configuration changes on the deployment manager synchronize with configurations for individual nodes on which the application will run.