By configuring a virtual host for each application, the
public URI can remain stable in the case of a configuration change.
For example, if the applications are moved to different servers, the
public URIs can be preserved by using a virtual host in the public
URIs hostname.
About this task
Virtual hosts can be used in the absence of a proxy server on a single
WebSphere® Application
Server computer
that contains the
IBM®
Engineering Lifecycle Management (
ELM)
applications. If the applications are to be moved to different servers, and you have configured a
distinct virtual host name for each application, then you can do this without adding a reverse
proxy. Simply change the DNS entry for the virtual host to resolve to the new server location. For
more information, see
DNS names in topologies.
Note: The following procedure must be
repeated for each installed application and must be performed before running the setup wizard and
registering applications.
Procedure
- In the administrative console, click .
- Click New, and enter a name for
your virtual host, for example, jts-server.
- Click OK, and then click Save
directly to the master configuration.
- Click the newly created virtual host link to open it.
- Under Additional Properties, click Host Aliases.
- Click New to create a
host alias. Enter * in the Host Name field and enter the HTTP or HTTPS
port number that the application server is configured to use (typically,
9080 for HTTP and 9443 for HTTPS). If you are planning on using only
HTTP or HTTPS, but not both, then only one alias is needed with the
corresponding port number. Otherwise, create two aliases, one for
the HTTP port and one for the HTTPS port. Click OK.
- To map the installed application to the virtual host that
you just created, click .
- Click the jts_war application link.
- Under Web Module Properties, click Virtual hosts.
- Under Virtual host, click the Down arrow, and select jts-server.
- Click OK, and then click Save
directly to the master configuration.
The virtual host configuration is complete. If you have set up DNS aliasing for the virtual host
to point to the WebSphere Application
Server, then
the server can be used immediately. However, if you want to test the configuration without using DNS
aliasing, you must add an entry in the hosts file on the server for which a browser is being used to
connect to the application. For example, add an xx.xxx.xxx.xxx jts-server where
xx.xxx.xxx.xxx is the IP address of the computer that hosts WebSphere Application
Server.
-
Repeat the preceding steps for all other installed ELM
applications. For example, configure these virtual hosts:
- rm_war with rm-server virtual host name with *
as host alias
- qm_war with qm-server virtual host name with *
as host alias
- ccm_war with ccm-server virtual host name with *
as host alias
-
Restart the WebSphere Application
Server after
making all of the changes.
-
When registering the applications in the Jazz® Team Server
setup, use the following discovery URLs for each application:
- For /rm choose
https://rm-server:9443/rm/scr
- For /qm choose
https://qm-server:9443/qm/scr
- For /ccm choose
https://ccm-server:9443/ccm/scr