IBM WebSphere Everyplace Access V5 Handbook for Developers and Administrators Volume IV: Advanced Topics

276 IBM WebSphere Everyplace Access V5, Volume IV: Advanced Topics

8.1.2 Multiple Web application servers using multiple host names

In some cases, the URL naming scheme used in 8.1.1, “Multiple Web application

servers using a single host name” on page 275 might not work. For example, an

enterprise might not want to organize Web pages and applications on existing

servers in order to support the URL naming conventions required. Another issue

is that servers can have different URLs when accessed from the intranet than

through Everyplace Connection Manager.

Many reverse proxy servers allow translation of the host name, not just the URL.

In this case, it is possible to use the configuration illustrated in Figure 8-2.

Figure 8-2 Multiple Web application servers using multiple host names

With this configuration, secure access can be allowed to any Web application

server in the mycompany.com domain. To allow access to a

http://wx.mycompany.com (x can be in that scenario 1, 2, or 3) using this

configuration requires the following:

򐂰 Everyplace Connection Manager needs a valid IP address on the Internet.

򐂰 The internal server’s host names must resolve to the IP address of the

Everyplace Connection Manager machine using a public DNS.

򐂰 An internal DNS server is used by the reverse proxy.

Clients

F

F

i

i

r

r

e

e

w

w

a

a

l

l

l

l

WECM

F

F

i

i

r

r

e

e

w

w

a

a

l

l

l

l

Internet IntranetDMZ

Port 80

Port 389

Port 5000

http://w1.mycomp.com

HTTP

Portal

WAS

Other

HTTP

Servers

Other

Application

Servers

Port 80 or 443

http://w2.mycomp.com

http://w3.mycomp.com

Reverse

Proxy

DB2

SecureWay

LDAP