This topic describes how to configure access to CM Server when
some sites may need to access CM Server by proxy or redirection from another
Web server.
In this configuration,
the other Web server redirects specific Web addresses to a CM Server process
running on the same host but using a different port, or running on a separate
host. The following common use cases require this type of configuration:
- CM Server and another Web server must run on the same host. Install
CM Server on a host that will not run any other Web servers. If this is impossible,
configure the other Web server to use ports that are not being used by CM
Server. If you cannot do this, you must configure CM Server to use ports not
used by the other Web server (see Changing the default CM Server HTTP port)
and optionally configure the other Web server to redirect Web addresses for IBM® Web
clients to CM Server.
- CM Server must run behind a firewall. To restrict access to CM
Server, a Web server running on the public side of a firewall can be configured
to pass specific URLs to an CM Server instance running on the other side of
the firewall.
CCRC or ClearQuest® Web client users must connect to the
server using this URL
- http://hostname:12080/TeamWeb/services/Team for WebSphere® Application
Server version 6.1 that is included with CM Server.
- http://hostname:9080/TeamWeb/services/Team for other
WebSphere Application Server versions.
Follow the instructions in this section to enable a proxied or
redirected configuration that provides access to CM Server from either of
the following Web servers:
- Apache HTTP Server
- Microsoft® Internet
Information Server (IIS)
Note: Instructions for configuring proxied or redirected access to
an IBM product
Web application are specific to the application and the Web server acting
as the proxy. Only the Web servers and IBM software products that are specifically
cited in this section can be supported in a proxied or redirected configuration.