Sun Java System Web Server 6.1 SP12 Administrator's Guide

Example 3: Intranet Hosting

A more complex configuration of the Sun Java System Web Server is one in which the server hosts a few virtual servers for an intranet deployment. For example, you have three internal sites where employees can look up other users’ phone numbers, look at maps of the campus, and track the status of their requests to the Information Services department. Previously (in this example), these sites were hosted on three different computers that had the names, and mapped to them.

To minimize hardware and administrative overhead, you want to consolidate all three sites into one web server living on the machine You could set this up in two ways: using URL-host-based virtual servers or using separate listen sockets. Both have their distinct advantages and disadvantages.

Figure 13–5 Intranet Hosting Using URL-host-based Virtual Servers

Intranet hosting using URL-host-based virtual servers

While URL-host-based virtual servers are easy to set up, they have the following disadvantages:

You could also set up the IP-address-based configuration with one listen socket per address:

Figure 13–6 Intranet Hosting Using Separate Listen Sockets

Intranet hosting using separate listen sockets

The advantages to IP-address-based virtual servers are:

The disadvantages are:

Both configurations require setting up name-to-address mappings for the three names. In the IP-address-based configuration, each name maps to a different address. The host machine must be set up to receive connections on all these addresses. In the URL-host-based configuration, all names can map to the same address, the one the machine had originally.

The configuration with multiple listen sockets could give you a minimal performance gain because the server does not have to find out the address the request came in on. However, using multiple listen sockets also results in additional overhead (memory and scheduling) because of the additional acceptor threads.