Getting Started with
Zeus Web Server 4.3
any manner or form (including photocopying or storing it in any medium by electronic means and whether or not transiently or incidentally to some other use of this documentation) other than in accordance with any applicable licence agreement or with the prior written consent of Zeus Tech-nology Limited. Any copies of this documentation must incorporate this notice.
Zeus Technology, the Zeus logo, Zeus Web Server (ZWS), Zeus Load Balancer (ZLB) and Zeus Extensible Traffic Manager (ZXTM) are trade marks of Zeus Technology Limited. Other trade marks used may be owned by third parties.
Adobe, Acrobat and Acrobat Reader are trademarks of Adobe Systems Incorporated. Microsoft, FrontPage, Internet Explorer are registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Netscape and Netscape Navigator are registered trademarks of Netscape Communications Corporation in the United States and other countries.
1.0 8-01 1 Zeus Technology Ltd
The Jeffreys Building Cowley Road Cambridge CB4 OWS United Kingdom Phone: +44 (0) 1223 525000 Fax: +44 (0) 1223 525100 Email: [email protected] Web: http://www.zeus.com
Getting Started with Zeus Web Server 4.3
Table of Contents
CHAPTER 1
Overview ...1
Introducing Zeus Web Server... 1
API Support and Integration... 2
Intended Audience... 3
Introducing This Manual... 4
Road Map... 4
Version Information... 5
Documentation Conventions... 5
Further Information... 5
CHAPTER 2
Quick Start Summary ...7
CHAPTER 3
Basic Concepts ... 9
Introduction... 9
Web Servers... 9
Introducing Web Servers... 9
Web Server Functionality... 10
Zeus Web Server Functionality...11
Virtual Servers...11
Introducing Virtual Servers...11
Types of Virtual Servers... 12
Managing Virtual Servers using Zeus Web Server... 12
Clusters... 13
Introducing Clusters... 13
Managing Clusters with Zeus Web Server... 14
Subservers... 14
Introducing Subservers... 14
Managing Subservers using Zeus Web Server... 15
Bandwidth Throttling... 16
Web Server Security... 16
Introducing Private Keys...17
Introducing Signed Certificates... 17
Introducing Self-Signed Certificates...17
Zeus Web Server Security Support...17
Logging...19
Monitoring Activity...20
Script-Based Management...20
CHAPTER 4
Installing Zeus Web Server ...23
Introduction... 23
Obtaining a License Key File...23
Preparing to Install...24
Installing as the root User... 24
Space Requirements...24
Browser Requirements...24
Installation Instructions...24
Unpacking the Download File... 25
Installing Zeus Web Server...26
CHAPTER 5
Starting Zeus Web Server ...29
Introduction... 29
Starting and Stopping Zeus Web Server...29
Starting Zeus Web Server...29
Stopping Zeus Web Server...30
Starting and Stopping Individual Components...30
Setting Up your Browser and Reader... 31
Accessing the Zeus Web Server Interface Pages... 31
Preparing to Publish a Web site...33
Creating a New Virtual Server...33
Using the Virtual Server Status Page... 38
Overview of the Virtual Server Status Page Layout... 39
Committing Configuration Changes... 40
Starting and Stopping Virtual Servers...42
Getting Started with Zeus Web Server 4.3
Publishing a Web site... 43
Viewing Your Web site... 43
CHAPTER 6
Feature Tour ...45
Introduction... 45
Using Logging... 45
Configuring Request Logging... 45
Configuring Error Logging... 47
Real-Time Monitoring... 47
Selecting Which Events to Monitor... 48
Configuring the Graph... 49
Using the Traffic History Pages... 49
Using the Traffic Overview Page... 50
Using the Web site Comparison Page... 51
Using the Cluster Traffic Analysis Page... 52
Introduction to Setting Up SSL Security... 53
Configuring SSL Support for a Virtual Server... 53
Using Bandwidth Throttling... 54
Creating a Virtual Server with Subservers... 55
Creating a Cluster of Web Servers... 57
CHAPTER 7
Simple Troubleshooting...59
Introduction... 59
If You have Forgotten Your Password...... 59
Contacting Support... 60
Glossary ...61
CHAPTER 1
Overview
1.1 Introducing Zeus Web Server
Zeus Web Server is a high performance web server with a scalable architecture that can host tens of thousands of websites on a single machine. It provides a reliable, secure web server that can handle tens of thousands of simultaneous connections and provides leading end-user response times and transaction throughput. Its flexible functionality can easily be integrated with existing systems, and its comprehensive and intuitive web-based configuration, management and administration system enables you to configure and run multiple websites easily, either locally or remotely, using a web browser. The web-based user interface supports web server clusters and centralized user management, enabling cost-effective administration of complex distrib-uted web server infrastructures. In addition to using the user interface, you can also manage and configure Zeus Web Server from the command line, from scripts.
Zeus Web Server is designed for, and used by, businesses that are supporting mission-critical websites, where speed and reliability are key. This includes Business-to-Business and Business-to-Consumer commerce sites, Internet Content Providers/Portals, ISPs offering shared web hosting services, and corporate Intranets.
It also integrates seamlessly with other Zeus products, providing a straightfor-ward migration and upgrade path to our Traffic Management and Mass Hosting products.
API Support and Integration
The web provides an accessible development platform, based upon open stan-dards, that ensures interoperability between applications. Zeus Web Server supports the following open-standard APIs:
• Server Side Includes (SSI)
SSI provides a simple means of organizing and managing web sites and is used extensively to provide attractive dynamic content. Zeus Web Server contains a powerful, efficient, recursive SSI parsing engine that signifi-cantly expands how SSI functionality can be used.
• Secure CGI sandbox system
Zeus Web Server is fully CGI/1.1 compliant and uses a unique sandbox environment to execute CGI programs safely by applying fine grain restrictions to CGI programs. It can place limits on the machine resources that CGI processes can consume, run programs under different UNIX IDs and run them in secure 'chroot' jails.
• FastCGI
FastCGI is an open standard for generating dynamic web content and authenticating access to web sites. It is an extension of the existing CGI standard, that eliminates many of its weaknesses. Zeus Web Server fully supports FastCGI applications.
• ISAPI
The Internet Server Application Programmers Interface (ISAPI) provides a vendor-independent way of extending the functionality of your web server. It is a widely-supported Microsoft-backed standard. Zeus Web Server fully supports ISAPI extensions and filters on all platforms and architectures.
• Java Servlets
Java’s threaded nature and object inheritance make it ideal for many web applications. Their platform independence enables Java Servlets to be distributed across a cluster of machines easily, which can include special-ized machines that are optimspecial-ized for the Java language, resulting in both
increased performance and system robustness. Zeus Web Server provides Java Servlet support through the native Jserv/Tomcat interface.
• NSAPI
NSAPI is a powerful, comprehensive web development toolkit with third-party support. Zeus Web Server provides NSAPI support to enable seam-less migration of web applications written for Netscape® Enterprise Server.
• Zeus Distributed Authentication and Content API
The Zeus Distributed Authentication and Content API (ZDAC) enables the web server to interact with external authentication servers and content generation servers over a TCP/IP socket interface.
• FrontPage
Zeus Web Server offers full support for Microsoft's and Netscape's web publishing applications. Microsoft FrontPage support is available on all Microsoft-supported UNIX platforms.
• PHP/Zend
PHP is an open-source server-side scripting language for creating dynamic Web pages for e-commerce and other web applications. Zeus Web Server provides a high-performance platform through the FastCGI interface. For more information, refer to the Zeus support website,
http://support.zeus.com/.
1.2 Intended Audience
This manual is aimed at users who have downloaded Zeus Web Server from the Zeus website to evaluate it, and customers who are running the software for the first time.
It assumes you are familiar with basic web server functionality, and basic UNIX commands.
1.3 Introducing This Manual
This manual introduces the basic concepts to help you understand and use Zeus Web Server effectively. It introduces some of its key features, and describes how to get started by configuring support for a basic website. It provides a guided introduction to the software and its capabilities, high-lighting key features, but does not provide a comprehensive guide to all its functions. This is provided in the online documentation.
Please send any feedback on this manual to [email protected].
Road Map
The Basic Concepts chapter introduces fundamental web server concepts and describes the functionality that Zeus Web Server provides. Read this chapter if you are unfamiliar with web server functionality or if you would like an overview of the Zeus Web Server functionality.
The Installing Zeus Web Server chapter describes how to install the Zeus Web Server.
The Starting Zeus Web Server chapter describes how to start Zeus Web Server, how to access its web-based user interface and how to create a Virtual Server. Read this chapter if you are running Zeus Web Server for the first time. The Feature Tour chapter describes how to use some of Zeus Web Server’s main features. It assumes that you are familiar with the basic web server concepts, and that you have set up your browser, can access the web server, and have created at least one Virtual Server. Read this chapter if you are evaluating Zeus Web Server for the first time, and would like to be introduced to some of its most interesting features.
The Simple Troubleshooting chapter describes what to do if you encounter simple problems with Zeus Web Server and how to contact support.
Version Information
This manual describes the functionality of, and uses screen shots from, Zeus Web Server version 4.3.
1.4 Documentation Conventions
This document uses the following conventions:
1.5 Further Information
For further information about running Zeus Web Server that is not covered here, please refer to our support website, at http://support.zeus.com, which provides an extensive FAQ, a range of product documentation and white papers, and access to our external mailing lists.
If you are unable to find what you are looking for on this website, or if you would like guidance in developing Zeus Web Server applications, please contact us at [email protected], quoting your customer account number in the subject header of your email.
Item Convention Example
Names of windows and buttons.
name Click the Apply changes button A new term, that is
being defined.
new term generate a private key
A variable item variable type http://your_machine_name
CHAPTER 2
Basic Concepts
2.1 Introduction
This chapter introduces fundamental web server concepts and describes the functionality that Zeus Web Server provides.
Read this chapter if you are unfamiliar with web server functionality or if you would like to read an overview of Zeus Web Server functionality.
2.2 Web Servers
Introducing Web Servers
In the simplest terms, web servers host web sites. One web server can host a number of different web sites: each web site is identified by an address that is used to access it. The web server makes pages available on the web by listening on the network for incoming requests for specific IP addresses, ports and host names.
The web site content is stored in a directory structure within the document root (or docroot) directory. The pages are either written and stored in their entirety, or can be dynamically generated. This is described in more detail in the following section.
Users access web sites using web browsers. Browsers request pages from the web server using URLs1, such as http://www.zeus.com/, and then display the pages returned by the server. Web servers can also receive information
back from browsers, for example, when someone fills in and submits a form. They can process this information in different ways and return further pages if required. Servers and browsers communicate with each other using the Hypertext Transfer Protocol (HTTP).
Web Server Functionality
Web servers host web sites, which can be thought of as being made up of two types of content:
• Static content is content that is stored in a file (such as an HTML page, or graphic image and so on) and sent to the browser to be displayed when requested. The content does not change unless someone modifies the file. Static files are generally created and then saved in the web site document root, so that they are ideally suited to being served up from a centralized file server.
For example, a movie review could be a page made up of static content. • Dynamic content needs to be generated in some way before the web
server returns it to the browser. Dynamic content is therefore generated on-the-fly, when requested, by calling a program that is run to produce the required output. Pages that contain dynamic content place servers under a heavier load and should be generated and served by fast
machines. There are many different ways of generating dynamic content, such as CGI, FastCGI, Java servlets, and NSAPI and ISAPI applications. For example, a cinema listings page that returns the listings for a speci-fied day could contain dynamic content. In this case the web server could query a database and build the result into a page before sending this page to the browser.
Web servers handle requests for information by locating and returning any static content files, and by calling the appropriate applications to generate dynamic content. Web servers can then incorporate all this information into the response that they return to the browser.
1. For more information about URLs, refer to the World Wide Web Consortium (W3C) web site, at http://www.w3.org/.
In order to be able to generate and return information securely and correctly, web servers also need to be able to control access to different applications and files, and display appropriate pages or information if the requested infor-mation does not exist, or cannot be accessed by the user making the request. It is also helpful to users if web servers can log access and activity information and be configured to manage the bandwidth available to different web sites, so that users can monitor and manage their web sites effectively.
Zeus Web Server Functionality
Zeus Web Server is a high performance, HTTP/1.1 compliant web server with a scalable architecture that can host tens of thousands of web sites on a single machine2.
It provides distributed content generation and authentication, with compre-hensive access control and supports the industry-standard APIs listed in API Support and Integration on page 20. Its functionality is described in more detail in the sections that follow.
2.3 Virtual Servers
Introducing Virtual Servers
A Virtual Server can be thought of as the environment that provides web server functionality for an associated web site3. Each Virtual Server can be configured to provide a specific level of functionality, such as the ability to run CGI scripts or ISAPI applications. It has its own unique address and docu-ment root that contains the content for its web site.
2. Note that some web servers host thousands of web sites, and some large web sites are hosted by hundreds of web servers.
3. If the Virtual Server supports Subservers, as described in Subservers on page 12, then it pro-vides the environment for a set of web sites.
Types of Virtual Servers
There are two different types of Virtual Server. The original version of the HTTP specification4 associated each web site with a single IP address. This meant that as additional web sites were added to a machine, more IP addresses also had to be added, which wasn't sustainable (as there are a fixed number of IP addresses available), and limited web server scalability. These Virtual Servers are referred to as hard Virtual Servers, which means that they are identified by a unique IP address and port combination.
To avoid these problems, HTTP/1.15 added a new way of identifying the desti-nation web site using first the IP address and port combidesti-nation, and then the contents of a Host Header (set to the requested host name). This enables one machine (with one IP address) to support multiple web sites, each of which is uniquely identified on that machine by its Host Header. These Virtual Servers are called soft Virtual Servers. A group of soft Virtual Servers can share a common IP address and port combination, and are distinguished using the Host Header field. This means that many web sites can be hosted on just one machine, without needing to configure it with many IP addresses. This is the most commonly used type of Virtual Server.
Zeus Web Server supports both hard and soft Virtual Servers. It can support thousands of hard Virtual Servers (limited only by the operating system TCP stack) and tens of thousands of soft Virtual Servers (limited only by the amount of available memory and Operating System scalability and not by the Zeus Web Server software).
Managing Virtual Servers using Zeus Web Server
You can use Zeus Web Server to set up, run and manage multiple Virtual Servers, each of which can be configured and controlled completely indepen-dently from the others. They can be stopped and started without affecting any others, and can also be monitored independently (described in Monitoring Activity on page 18).
4. HTTP/0.9, defined in http://www.w3.org/Protocols/HTTP/AsImplemented.html 5. The HTTP/1.1 RFC can be found at http://www.w3.org/Protocols/rfc2616/rfc2616
Each Virtual Server can have individual bandwidth limits specified (as
described in more detail in Bandwidth Throttling on page 14), ensuring that no one Virtual Server can use more than its share of system resources. This can help guarantee particular levels of service for each Virtual Server, and also help contain any denial of service attacks.
Note:
i
Because SSL security is configured for particular IP address and port combina-tions, this means that hard Virtual Servers can be configured independently with SSL security, but soft Virtual Servers cannot.
Refer to Creating a New Virtual Server on page 33 to find out how to create a new Virtual Server using Zeus Web Server.
2.4 Clusters
Introducing Clusters
A cluster is a group of computers, each of which is running the same set of Virtual Servers (with the same configurations). This means that they are effectively hosting their web sites across multiple machines, so that they act together like one “big” web server, commonly called a “web server farm”. Clusters are usually run in conjunction with some sort of intelligent load balancing mechanism that distributes incoming web requests across the web servers in the cluster. This can be used to ensure that the web servers are loaded evenly, and that no particular web server is overloaded with requests, particularly if other web servers have spare capacity available. It can also mean that if one machine fails then its load is shared transparently between the others, thus providing fault tolerance. There are a number of different load balancing solutions available, implemented both in hardware and soft-ware, including Zeus Load Balancer6.
6. For more information about Zeus Load Balancer, refer to http://www.zeus.com/products/zlb/
Clusters enable you to increase your web serving computing power easily by simply adding more computers to the cluster. This can often be cheaper and involve less downtime than upgrading a single central server. You can also store your static web pages using a centralized networked file system (NFS) that can be accessed by all machines in the cluster.
Managing Clusters with Zeus Web Server
Zeus Web Server makes it as simple and straightforward to set up and manage multiple web sites on a cluster of web servers as it is to set them up on just one. The Administration Server manages and coordinates all the web serving components within the system (which can also include other products such as Zeus Load Balancer6). It holds the master configuration for all the web servers in the cluster, and automatically updates their configuration at the same time, thus ensuring consistency across the cluster. This means that you can deploy web site configurations across the entire cluster at the click of a button, and can monitor the real-time activity of the cluster.
Zeus Web Server clusters therefore provide an easy way of hosting multiple web sites across multiple machines, so that you can easily add machines as required, and eliminate single points of failure in your web hosting network. Refer to Creating a Cluster of Web Servers on page 284 for more information about setting up a cluster using Zeus Web Server.
2.5 Subservers
Introducing Subservers
Hosting providers often want to be able to run many web sites with similar configurations. For example, they might want to be able to offer a small set of “service offerings” (levels of web site functionality) with an associated pricing system, and an easy way of moving customers between them. Subservers provide an easy way of configuring, managing, supporting and scaling lots of similarly configured web sites. They enable you to set up the web site functionality just once, in just one place (the Virtual Server), and then use it to support a large number of separate web sites. This type of
Virtual Server has multiple document roots, each of which is accessed as a separate web site. Each of these document roots is associated with its own Host Header, and is called a Subserver.
Subservers make it simple to set up multiple web sites configured with the same functionality whilst avoiding the memory and disk usage overheads of running hundreds of Virtual Servers. They can be configured and managed easily just by configuring and managing one Virtual Server.
Managing Subservers using Zeus Web Server
Zeus Web Server enables you to set up Subservers by simply creating a Virtual Server with Subserver functionality enabled.
You can then add Subservers to the Virtual Server simply by adding subdirec-tories to the Virtual Server document root7: you do not need to configure any other information or stop and start the Virtual Server. This means that adding a new web site can be as easy as simply creating a new directory. Each of these Subservers supports the functionality provided by their “hosting” Virtual Server. When the Virtual Server receives a request for a Subserver, it simply checks to see whether it has a document root directory of the same name as the request’s Host Header. If so, it returns the appropriate file from that docu-ment root.
Customers can simply be given access to a Subserver document root (providing them with whatever functionality the associated Virtual Server is configured with), and they can then maintain and update their web sites in the usual way.
7. Because operating systems usually provide a limit to the number of subdirectories that can be supported within a directory (and therefore to the number of document root directories that can be supported), the Zeus Web Server uses a hashing scheme that extends this and enables approximately 70 billion (236) document root directories or Subservers to be sup-ported on one Virtual Server. This means that in practice other limits constrain the total number of document roots.
2.6 Bandwidth Throttling
Bandwidth throttling enables you to limit the bandwidth available to any given web site. It can be used to ensure that no single web site uses all the available bandwidth, thus compromising the availability of other web sites hosted by the same web server.
Zeus Web Server makes it easy for you to specify the bandwidth that is avail-able to each Virtual Server (or Subserver), as described in Configuring Band-width Throttling on page 202.
2.7 Web Server Security
Introducing Web Server Security
Web server security is made up of a number of different aspects. To be secure, web servers cannot simply send pages straight to clients (browsers) in a form that can be intercepted and read by anybody. Web servers must be able to ensure that only the client that is supposed to be reading (or editing) some-thing is able to do so. This enables sensitive information such as names, addresses and credit card numbers to be transmitted securely between web servers and web browsers.
The table below summarizes the different aspects of web server security and how these issues can be solved using a particular security implementation, called SSL (Secure Sockets Layer) security:
Aspect Issue Solution
Identity Are you really talking to the person or web site that you think you are?
Web servers authenticate them-selves to browsers using public and private keys, and certificates.
Introducing Private Keys
The first step in configuring web site security is to generate a private key. This key is used to unlock the coded communication that is intended only for the key holder.
Introducing Signed Certificates
Signed certificates are certificates that are signed by a recognized Certificate Authority (CA), such as VeriSign, vouching for your identity. If you are going to use a publicly-recognized signed certificate, you will need to purchase one from a recognized CA who will use the information that you provide to check that you are who you say you are.
Once you have received your requested public certificate from the CA, you need to configure your Virtual Server to use it.
Introducing Self-Signed Certificates
While waiting for a signed certificate, you can generate a self-signed certifi-cate that you can use for web site security testing. A self-signed certificate
simply states that you are who you say you are, without any independent veri-fication. Note that it is not necessary to do this; you can use a signed certifi-cate, without having used a self-signed certificertifi-cate, but it does enable you to develop and test your system first.
Zeus Web Server Security Support
Zeus Web Server provides full support for 128 bit SSL v3 and client-side X.509 certificates. It also supports hardware crypto-accelerators that can be used to
Privacy Is anyone else reading the infor-mation you are sending or receiving?
Web servers agree an Encryption Key with the browser and use it to encrypt all information they send. Integrity Are you reading what was
actu-ally sent to you, or has it been modified in transit?
Web servers send each encrypted message with a Message Authenti-cation Code.
carry out the SSL processing in hardware, and so reduce the load on the machines running the web servers8.
The Zeus Web Server interface makes it extremely easy to set up SSL-enabled web sites. It can generate private keys, self-signed certificates and certificate signing requests that can be sent to a recognized CA. It is integrated with the VeriSign web site, and can lead you through the process of buying a signed certificate. It also provides clustered support for SSL, so that you can set up SSL-secured web sites across a cluster.
For more information about setting up SSL, refer to Setting up Virtual Server SSL Security on page 68.
8. Note that most of the SSL processing overhead occurs when the secure connection to the Virtual Server is being established. Once established, an SSL connection uses little addi-tional load.
2.8 Logging
Logging enables you to record information about your web server system. Zeus Web Server can record the following types of information:
• Error logs record information about Zeus Web Server’s activity. These logs are categorized in the following way:
• Request logs record information about every request received by each Virtual Server. You can specify exactly what information is logged, and use these logs in conjunction with the Traffic History pages (introduced in the following section) to provide the basis for detailed analysis of your web site usage trends.
Zeus Web Server enables you to switch request logging on and off, specify where the logs are written to and configure which fields are included in the logs (on a per-Virtual Server basis), so that you can include exactly the information that you need and no more.
For more information about configuring logging, refer to Configuring Request logging on page 165 and Error Handling on page 173.
Information Type Marked Indicates
Status information INFO Normal web server activity. For example, the web server starts and stops.
Warning information WARN There was a problem starting a resource such as a Virtual Server, but it has still been started. For example, the specified global .htaccess file could not be found, and so the Virtual Server was started without it.
Error information SERIOUS There was a problem starting a resource such as a Virtual Server, that prevented it from starting. For example, a Virtual Server’s docu-ment root could not be found.
Fatal information FATAL There was a problem that prevented the product from running. For example, an instal-lation file has been corrupted and so Zeus Web Server is unable to run.
2.9 Monitoring Activity
Zeus Web Server enables you to monitor your web server activity in the following ways:
• Real-Time Monitoring
This page displays real-time statistics that enable you to monitor the activity of the web servers on any of the machines in your cluster. It displays a real-time graph, that can be updated every second, showing how often various events occur within Zeus Web Server. You can monitor a wide range of events, such as how many requests the web server is answering, how many times a specific HTTP error page is returned, or how often a particular piece of functionality is used. Refer to Real-Time Moni-toring on page 73.
• Traffic History
These pages9 display dynamically-generated graphical information about web site activity (the hits or bytes transferred from each web site over the previous day or week). These pages display graphs showing recent activity for the selected categories of information (such as machines or Virtual Servers and so on). Refer to Using the Traffic History Pages on page 78 for more information about using this.
Note that this activity information is held separately from the request and error logs (introduced in the previous section).
2.10 Script-Based Management
Zeus Web Server provides an easy-to-use web-based interface for configura-tion, management and administration tasks, which calls a set of underlying scripts. Sometimes, however, a task may need to be repeated hundreds of times, say. In this case it can be easier to simply run the scripts directly from the command line, or combine multiple commands in a script of your own. This can be helpful if you are performing repetitive tasks, or are performing a complex task made up of many individual small steps.
For more information about using scripts and manipulating configuration files, refer to Scripting Overview on page 369.
CHA PTER 3
Quick Start Summary
Install Zeus Web Server See Installing Zeus Web Server on page 23 for details. Make a note of the Administration Server URL returned to you during the installation.
Access The Web-based User Interface Enter the URL returned in the previous step into your browser. See Accessing the Zeus Web Server Interface Pages on page 31 for details.
Create a Virtual Server
Click the Virtual Server link in the Web Controller menu. See Creating a New Virtual Server on page 33 for details.
Start the Virtual Server Select the Virtual Server and click the Start button. See Starting and Stopping a Virtual Server on page 40.
View its Web site Click the Virtual Server’s web site address link. See Viewing Your Web Site on page 41 for details.
CHA PTER 4
Installing Zeus Web Server
4.1 Introduction
This chapter describes how to install Zeus Web Server.
4.2 Preparing to Install
Installing as the
root
User
In order to bind to the default HTTP port (port 80), the web server must
initially run as root10. It is therefore recommended that you install the web server as root.
Space Requirements
Zeus Web Server requires approximately 35 MB of disk space during installa-tion. After installation, you can clear the intermediate directory that was created when you unpacked the compressed file, so that Zeus Web Server then takes up approximately 15 MB.
10. After Zeus Web Server starts up and binds to port 80, it runs as the user and group that is specified for it during the installation process (described in Installing Zeus Web Server on page 25)
Browser Requirements
You will require a graphical browser to access the Zeus Web Server user inter-face. We suggest using recent versions of widely available browsers such as Netscape® Communicator or Microsoft® Internet Explorer.
Note that all screen shots shown in this manual are based on
Netscape® Communicator 4.75. The appearance of screen shots and dialog boxes may vary with different browsers and browser versions.
4.3 Installation Instructions
Unpacking the Download File
You will now have a compressed tar file containing Zeus Web Server, with a file name in the form Zeus_ProductVersion_OS.tgz, where
ProductVersion refers to the current Zeus Web Server version number and
OS refers to the operating system that you are installing on.
Extract this to a temporary directory using your normal tar/gzip11 tools, and run zinstall from that directory, as described in more detail in the next section.
For example, on a Linux system with GNU tar installed, enter:
$ tar zxvf Zeus_42_Linux-glibc2.1.tgz
You will then see something similar to the following, as the system unpacks the file: Zeus_42_Linux-glibc2.1/common/ Zeus_42_Linux-glibc2.1/common/perl/ Zeus_42_Linux-glibc2.1/common/perl/miniperl Zeus_42_Linux-glibc2.1/common/perl/ZeusOS.pm Zeus_42_Linux-glibc2.1/common/start-zeus Zeus_42_Linux-glibc2.1/common/stop-zeus Zeus_42_Linux-glibc2.1/common/restart-zeus Zeus_42_Linux-glibc2.1/common/rc.d/
11. gzip is available on the Internet. For example, see http://sunsite.org.uk/packages/gnu/gzip/gzip-1.2.4.tar
Zeus_42_Linux-glibc2.1/zinstall Zeus_42_Linux-glibc2.1/admin-4.1a2.tar Zeus_42_Linux-glibc2.1/web-4.1a2.tar Zeus_42_Linux-glibc2.1/webadmin-4.1a2.tar Zeus_42_Linux-glibc2.1/snmp-4.1a2.tar Zeus_42_Linux-glibc2.1/admin_lang_en_gb-4.1a2.tar Zeus_42_Linux-glibc2.1/webadmin_lang_en_gb-4.1a2.tar Zeus_42_Linux-glibc2.1/web_lang_en_gb-4.1a2.tar Zeus_42_Linux-glibc2.1/admin_lang_en_us-4.1a2.tar Zeus_42_Linux-glibc2.1/webadmin_lang_en_us-4.1a2.tar Zeus_42_Linux-glibc2.1/web_lang_en_us-4.1a2.tar Zeus_42_Linux-glibc2.1/LICENSE Zeus_42_Linux-glibc2.1/MANIFEST
Installing Zeus Web Server
To install the product, change directory into the directory just created, called
Zeus_ProductVersion_OS, and run:
$ ./zinstall
You are installing a package built for Linux-glibc2.1
Zeus Installation Program - Copyright (C) Zeus Technology 2002
The Zeus installer then takes you through the installation process in the following way:
1) If you are not installing as root then it asks you if you want to continue. 2) It shows you a copy of your license agreement and asks you to confirm
your acceptance. Read the agreement and type accept to confirm and continue your installation.
3) It asks where you want Zeus Web Server to be installed. Enter the name of a new directory (which is created automatically as part of the installa-tion process). We recommend that you specify /usr/local/zeus, but you can install Zeus Web Server anywhere on your filesystem. The direc-tory which you install into will be referred to by the environment variable
$ZEUSHOME
4) It asks what type of installation you want to perform. Enter 1 to select
server component and its management system (the Administration Server) on the same machine12.
5) It asks you to enter the full path and name of your license key file. If you have a license key, you should enter the path to the key at this point. If you do not have a license key, then Zeus Web Server will be configurable, but you will not be allowed to start any Virtual Servers. You can obtain a license key (full or evaluation) by using the Licensing Information page once Zeus Web Server is installed.
6) It asks you for a password that you will use to access the Administration Server. Enter your chosen password, and then enter it again to confirm it13.
7) It asks you if you would like to enable SNMP support for Zeus Web Server. Enabling support means that web server statistics can be monitored via a 3rd party package such as HP OpenView. If you choose to enable SNMP, you will also be prompted for an SNMP community string. This is used to restrict access to who can retrieve SNMP variables across the network. 8) If you are installing as root, it asks you to specify which UNIX user and
group the Zeus Web Server process will run as. Note that because Zeus Web Server supports a number of different application APIs, it is strongly recommended that you ensure that any applications and scripts run as unprivileged users so that there is no danger of the security of the system running Zeus Web Server being compromised.
The default user with no privileges is usually nobody and the default group with no privileges is usually nogroup or nobody, depending on which version of UNIX you are running. If, however, you have set up other
12. Option 2, Stand-alone install of admin server, installs just the Administration Server on a separate machine. If you are setting up a web server cluster (described in more detail in
Clusters on page 11), you can use option 3, Clustered install of web server, to install just the web server component on each of the machines in the cluster.
13. Note that you can subsequently change this password, if required, as described in the Zeus Web Server User Guide.
users and groups on the Zeus Web Server machine, you can specify them here.
9) If you are installing as root, it asks you whether Zeus Web Server should be started automatically at boot time.
10) It starts up the Zeus Web Server Administration Server, and reports where it can be found, in the form:
** To configure the Zeus Web Server, please go to ** http://yourmachinename:controlport
** and login as 'admin' with your admin password.
Make a note of this URL as you will need it to connect to and use Zeus Web Server.
11) Zeus Web Server starts automatically.
Access the Zeus Web Server from your web browser using the URL pro-vided in step 10.
4.4 Obtaining a License Key File
This section applies only if you have installed Zeus Web Server without speci-fying a license key. Some of the functionality of Zeus Web Server is only available when it is licensed. You will be able to configure Virtual Servers using your browser, but not be able to start them (and thus serve content) without a license key.
Obtaining a license key is done by going to the Licensing page. This is listed in the Web Controller Menu which is at the left side of your browser window. The Licensing page will show the machines configured as web servers, and a link to obtain a license for unlicensed machines.
If you are ready to purchase, then you can obtain a full non-expiring license key. However, if you wish to evaluate Zeus Web Server, then an evaluation license is available which will allow you to use Zeus Web Server for a number of days before the key expires.
Please follow the instructions given to obtain your license key. Some of the details about your machine and network will be automatically filled in. Once
you have saved your license key to disk, then you can install it by using the
Install a new License Key option on the Licensing page. Enter the pathname of the license key and click the Install button.
Once your installation of Zeus Web Server is licensed, you will be able to start Virtual Servers from the Virtual Server Status page.
Note:
i
Specifying a directory instead of a file when installing your licence key may confuse your browser and cause it to lock up.
CHAPTER 3
Starting Zeus Web Server
3.1 Introduction
This chapter assumes that you have installed Zeus Web Server, as described in
Zeus Web Server Getting Started Guide. It describes how to start Zeus Web Server, how to access its user interface pages and how to create a Virtual Server.
Read this chapter if you are running Zeus Web Server for the first time. The next chapter describes how to configure your Virtual Servers.
3.2 Starting and Stopping Zeus Web Server
Starting Zeus Web Server
Normally Zeus Web Server starts automatically once you have installed it. To access it follow the instructions in the next section.
If, for any reason, however, Zeus Web Server has not started, you can start it explicitly by entering the following command, as the user that you installed under (usually root):
$ installation_dir/start-zeus
Stopping Zeus Web Server
Similarly, you can stop Zeus Web Server from the command line as the user that you installed under (usually root) in the following way:
$ installation_dir/stop-zeus
Where installation_dir is the directory that you installed in. This stops all the Virtual Servers on Zeus Web Server.
Warning:
!
Once you have stopped Zeus Web Server, you will no longer be able to access the user interface pages, or any of its Virtual Servers or the web sites that they are running.
Starting and Stopping Individual Components
The start-zeus and stop-zeus commands start and stop all the installed components. These include the administration component, which enables you to access the user interface pages, and the web server component, which runs all the Virtual Servers. If you have other Zeus products installed there will be other components too.
You may want to leave the web server component running, and just start the administration component when you want to access the user interface pages. In this case you can start the administration component in the following way:
$ installation_dir/admin/rc start
To stop the administration component, do the following:
3.3 Setting Up your Browser and Reader
This section describes some of the browser and PDF reader settings that you can specify in order to maximize the functionality of the User Interface. • Multiple Language Support
The user interface pages can be displayed in any of the languages that are available as a Zeus Web Server language pack. To display them in one of these languages, simply configure that language as your preferred language in your browser settings. These can typically be found in the browser’s options or preferences menu.
• Viewing the Virtual Server tree structure
It is recommended that you enable cookie support in your browser. This enables the expanded state of your Virtual Server tree to persist as you move between pages. All the functionality will still work if you do not enable cookie support but you may find that you need to keep expanding your Virtual Server tree every time you access the Virtual Server Status page.
• Viewing the online documentation
The online documentation is displayed using the Adobe Acrobat reader14. It is recommended that you set your Adobe Acrobat reader settings to display in continuous mode. Do this by accessing the Adobe File/Prefer-ences/General dialog box. Set Default Page Layout to Continuous.
3.4 Accessing the Zeus Web Server Interface Pages
To access the Zeus Web Server interface pages, enter the URL that was returned to you during the installation process (as described in the Zeus Web Server Getting Started Guide) in your browser location bar. This usually has the form: http://YourMachineName:AdminServerPort, where
yourmachinename is the name of the machine on which you installed Zeus
Web Server, and AdminServerPort indicates the port that it is running on
(usually port 9090).15
Your browser displays the login dialog box:
Enter admin into the User Name field, and enter the password that you chose during the installation process into the password field. Note that both of these fields are case-sensitive.
Zeus Web Server displays an empty Virtual Server Status page:
15. This information is also logged in the Administration Server log file, that can be found in installation_dir/admin/log/errors.
Note:
i
You can bookmark this page, so that it is easy to return to.
This page provides access to the Virtual Server management and configuration pages for controlling your Virtual Servers.
Note that if you install other Zeus products, the page also displays links to their associated management and configuration pages.
The next step is to create a Virtual Server, as described in Creating a New Virtual Server on page 33. For more information about using this page, refer to Basic Tasks on page 55.
3.5 Preparing to Publish a Web Site
Before setting up your first Virtual Server and publishing a web site, you should have the following:
• An address for the web site, that visitors will use to access it. You will need to register the domain name, and then set up a DNS entry for it before using it.
For example, to set up the web site www.mywebsite.com, register the
mywebsite.com domain name and then set the DNS entry for
www.mywebsite.com to your Zeus Web Server computer’s IP address. • The web pages, associated files, and applications that provide the content
for your web site.
3.6 Creating a New Virtual Server
The first step in using Zeus Web Server is to create at least one Virtual Server. A Virtual Server hosts web site content and provides the functionality used to generate its dynamic component. Virtual Servers are described in more detail in Virtual Servers on page 9.
To create a new Virtual Server, simply do the following: 1) Click the Virtual Server link in the Web Controller menu.
2) Fill in the fields on this page in the following way:
Set this field... ... to...
Virtual Server Name
a name that will help you identify this Virtual Server easily. It can contain letters, numbers, hyphens, dots and underscores, but no spacesa (for example, ‘personal’, ‘secure’, or
‘www.mywebsite.com’). It also cannot start with an under-score.
Zeus Web Server uses this name to identify this Virtual Server to you in the Virtual Server Status page, but it will not be seen by people viewing and using its web site.
Host Name and Port
the URL that clients will use to visit the Virtual Server’s web sites. It can be made up of letters, numbers, hyphens (-) or dots (.), but no spaces or underscores. You must ensure that you have registered this domain name and set up a DNS entry for it, as described in Preparing to Publish a Web Site on page 33. Note that you should also include the port number that the web site is running on if this is anything other than the default HTTP port (port 80). This will not normally be the case, but might be useful for you to do if you are developing and testing a new web siteb.
Server Comment comments about the Virtual Server. This text is displayed in the Virtual Server Status page, so you can use it to record any information that you want to associate with the Virtual Server. Document Root the full name and path of the subdirectory in which you are
storing the Virtual Server’s web site content. Note that this is the full path and so must start with a “/”.
Aliases specify aliases for your web site. Virtual Server aliases are a way of specifying “alternative web addresses” for a web site: the user goes to the same web site, and sees the same web pages, whichever alias is used. It can be helpful to specify a number of alternative addresses that you think users might use to access your web site.
For example, you could specify www.mywebsite.co.uk to be an alias for www.mywebsite.com. c
Specifying an alias of * means that this Virtual Server will be treated as the default Virtual Server for the IP addresses that it is binding to. This means that the Virtual Server will process requests for any host headers that do not match any configured aliases or host names for these IP addresses. Do not configure more than one Virtual Server with an alias of * on any IP address.
You can also configure a Virtual Server to respond to a number of web sites within a domain. For example you could specify *.accounts.mybank.com and *.mybank.co.uk, so this Virtual Server will serve products.mybank.co.uk and platinum.accounts.mybank.com.
You can only use * for a wildcard as the first character of the alias. It is not possible to specify www.*.mybank.com Note that in the same way that you must register a domain name before using it as a web site address, you must also register any domain names that you wish to specify as aliases. Note that this field can only be specified for Soft Virtual Servers.
3) Click the Create Virtual Server button.
Zeus Web Server creates a new Virtual Server and adds it to the tree displayed on its Virtual Server Status page, and displays its configuration pages (described in Using the Configuration Pages on page 89).
Warning:
!
If you are already running one web server (perhaps because you are evaluating Zeus Web Server beside an existing web server), then you must ensure that you specify a port (other than port 80) in the Host Name and Port section.
Webmaster email address
the email address of the person responsible for this web site. Zeus Web Server automatically includes this email address in its default error web pagesd. This enables people viewing your web site to report any problems more easily.
If you do not specify an address then Zeus Web Server uses webmaster@web_site_address (where
web_site_address is your host name with any leading www. removed).
Clone server the name of another Virtual Server on which to base this one (if any). Either accept the default configuration settings by leaving the drop down box set to [skeleton config], or, if you already have a Virtual Server that is set up differently, then you can select its name to specify that these settings should be copied instead.
Note that the drop down box is not displayed if you have a very large number of Virtual Servers. In this case you should enter the name of the Virtual Server in the field instead.
a. The Virtual Server Name is used as the name of its configuration file.
b. Note that if you are running Zeus Web Server as a non-root user, you will only be able use ports greater than 1024.
c. Users using an alias to access your web site will continue to see that alias displayed in their browser location bar. Aliases are not the same as HTTP redirection, in which users accessing one web site are automatically redirected to another (whose web site address is then displayed in their browser location bar).
d. For information about changing the default HTTP error pages, refer to Customizing HTTP Error Pages on page 173.
This is because the existing web server is already listening to port 80 and so your Zeus Web Server Virtual Servers must be associated with a different port.
3.7 Using the Virtual Server Status Page
The Virtual Server status page displays all your Virtual Servers and their current status. It enables you to create new Virtual Servers, and to monitor and manage them.
This section describes the page layout and how to use this page.
Overview of the Virtual Server Status Page Layout
The Virtual Server status page contains the following: • Main Screen area
The main screen area displays a tree of your configured Virtual Servers,
Border bar
Main Screen Area
ordered by Virtual Server name. Virtual Servers can be grouped together, as described in Grouping Virtual Servers on page 56.
Each Virtual Server is displayed with its name and its web site URL. When the Virtual Server is running, the URL (usually16) provides a hyperlink to the Virtual Server’s web site. Each Virtual Server is also displayed with the following set of status icons:
• Other Icons
• To view details about a problem, click the Diagnose icon:
• To edit a Virtual Server, click the Configure icon: • Button Set
The buttons under the Virtual Server tree enable you to carry out actions on the selected Virtual Servers.
• Web Controller menu
The Web Controller menu provides links for creating Virtual Servers and
16. There is no hyperlink if the Virtual Server has the Subserver functionality set (see Configur-ing Subservers on page 253).
Icon Name Icon ... indicates that...
Running State Icon
the Virtual Server is running.
the Virtual Server was not started successfully. Click the Diagnose icon for further information about the problem.
the Virtual Server is stopped.
the Virtual Server was not stopped successfully. Click the Diagnose icon for further information about the problem.
Configuration Changes Icon
the Virtual Server’s configuration has changed but the changes have not yet been committed. See Commit-ting Configuration Changes on page 61 for more infor-mation.
groups of Virtual Servers. It also provides the Find VS field, described in
Searching for a Virtual Server on page 59. • Border bar
The border bar provides the following buttons:
Starting and Stopping a Virtual Server
Virtual Servers can be running or stopped. A running virtual server can receive and process traffic; a stopped virtual server does not, and uses no resources on the web server.
When you create a new virtual server, it is not running. You must start it when you want it to be active.
To start a virtual server, select the virtual server from the list in the Main Screen Area. Then, click the ‘Start’ button in the Button Set.
To stop a virtual server, select the virtual server from the list in the Main Screen Area and click the ‘Stop’ button in the Button Set.
Committing Configuration Changes
The configuration settings that a virtual server is using (whether it is running or not) are referred to as the ‘Committed Configuration’. If you start or restart a virtual server, it will use the committed configuration settings.
When you make configuration changes using the Administration Server, they do not take effect immediately. Once you have made your changes, which may involve editing several different parts of the configuration, you can then review and commit them.
Button Name Use it to...
Documentation ... view the online documentation. Home ... return to the Virtual Server Status page.
You will see a yellow ‘star’ icon light up in the Administration Server if you have uncommitted changes, and you will receive a warning each time you make a change.
To commit your changes, click on the yellow star or on the warning text. This will take you to a page where you can review your changes, and choose either to commit them or to revert them back to the previously committed configu-ration.
Committed changes take effect immediately on a running virtual server. On a stopped virtual server, they take effect when the virtual server is next started.
3.8
Publishing a Web Site
In order to publish a web site on a Virtual Server, do the following: • Put your pages and any associated files and programs into a directory
structure under the Virtual Server document root17.
• Ensure that the Virtual Server is running as described in Starting and Stopping Virtual Servers on page 63.
3.9 Viewing Your Web Site
When the Virtual Server is running, you can click the web site address link to view its web site18. Your browser then displays the Virtual Server’s home page in a new window. As long as the web site’s Virtual Server displays a green Running State icon (indicating that it was started successfully and is running), users can access it.
17. You can also put content into any directories that you have mapped to the document root directory structure using the URL mapping functionality (refer to Configuring URL Mapping
on page 126 for more information).
You can now maintain and update the web site in the following ways: • You can edit the files in its document root.
• You can modify its configuration as described in Using the Configuration Pages on page 89.
• You can monitor it using the Traffic History pages (as described in Using the Traffic History Pages on page 78).
• You can analyze its traffic by parsing the log files (see Configuring Request logging on page 165 and Error Handling on page 173).
CHA PTER 4
Feature Tour
4.1 Introduction
This chapter describes how to use some of Zeus Web Server’s main features. It assumes that you are familiar with the basic web server concepts, introduced in Basic Concepts on page 7. It also assumes that you have set up your browser, can access the web server, and have created at least one Virtual Server as described in Creating a New Virtual Server on page 33.
Read this chapter if you are evaluating Zeus Web Server for the first time, and would like to be introduced to some of its most interesting features.
4.2 Using Logging
Zeus Web Server records request and error information independently. It enables you to switch request logging on and off, to configure which fields are included in the logs, and specify the files to which the logs are written. For more details about the type of information that is logged, refer to Logging on page 17. All log files can be saved as ASCII text files or in binary format.
Configuring Request Logging
The request log records information about each request received by the Virtual Server. Configure request logging as follows:
1) Access the request logging page by clicking the Request Logging link in the configuration pages menu.
2) Enable the request logging functionality by clicking the appropriate radio button.
Note that request logging is switched off by default, and it is recom-mended that you switch it on when setting up a new system.
3) Enter the full path and name of the file in which you want the logging information to be stored. To prevent users from viewing the log file, it is advisable to locate it outside the Virtual Server’s document root.
4) Specify the log file format; that is, what fields are to be included in each log entry. By default, log file entries are in NCSA Common Log Format, which is the format most commonly understood by third-party log-analy-sis tools. You can change the format string to any one of a number of pre-defined formats, or create a customized string of your own. Using a customized string is useful because it gives you complete control over the content and layout of your log files.
You can configure the log file format in one of the following ways: • To enter a customized format string, click the appropriate radio
but-ton, then enter the string. For more information about the different fields that you can log, and how to specify them, see the online help. • To use a pre-defined format string, click the appropriate radio button,
then select a format from the drop down list. 5) Click the Apply changes button.
Ensure that you commit the configuration for the changes to take effect, as described in Committing Configuration Changes on page 40.
The log file is created as soon as a user requests a file from your Virtual Server. The log file has the name you gave it with the current date appended to it. Each day a new log file is created and the day’s requests are recorded there. For example, if you enter /logs/myfile as the log file name, then log entries on the 30th April 2001 are saved in the file
/logs/myfile.20010430.
You should bear in mind that logging reduces performance very slightly and consumes disk space. If this is an issue then note that the Binary Logging Format is the most efficient and compact logging format to use.
Configuring Error Logging
The error logs record information about the rest of each Virtual Server’s activity, such as when it is started and stopped, and any configuration prob-lems encountered. Error logging is always switched on and cannot be switched off.
By default, all Zeus Web Server error logs are written to a central error log file,
%ZEUSHOME%/web/log/errors. However you can configure a specific error log file for an individual Virtual Server in the following way:
1) Access the error handling page by clicking the Error Handling link in the configuration pages menu.
2) In the Error Logging section, enter the full path and name of the new error log file.
3) Click the Apply changes button.
Ensure that you commit the configuration for the changes to take effect, as described in Committing Configuration Changes on page 40.
When a Virtual Server has an individual error log file specified for it, this is the one that is used while the Virtual Server is running19.
4.3 Real-Time Monitoring
Real-time monitoring enables you to monitor the activity of any of the web servers on different web server machines in your cluster. It displays a real-time graph, that can be updated every second, showing how often various events occur within Zeus Web Server. You can monitor a wide range of events, such as how many requests the web server is answering, how many times a specific error page is returned, or how often a particular piece of func-tionality is used.
19. The fact that the Virtual Server has been started is recorded in the global log file, but the fact that it is running along with all subsequent information, until it is stopped, is recorded in the local file.
The graph displays a separate colored line for each event that you are currently monitoring. The key below the graph displays a brief description of each monitored event, and the color that represents it.
Access the real-time monitoring page by clicking the Real-Time Monitoring
link in the Web Controller menu:
Selecting Which Events to Monitor
To select which events to monitor, click the Change monitored variables
button. This displays a list of all the events that can be monitored, grouped under various headings. Individual events that can be monitored have a brief
description, and a check box to enable you to select them. Use the list in the following way:
• To select an event so that it is monitored and displayed on the graph, click its check box.
• To expand a group heading so that you can see the events within it, click its plus sign.
Once you have selected the events that you want to monitor, click the Apply changes button to return to the graph.
Note:
i
Although you can monitor any number of events, selecting a large number can make the graph difficult to read.
Configuring the Graph
You can configure the real-time graph in the following ways:
• You can configure how often the graph is updated by entering a sampling period (in seconds).
• You can configure the total time period that the graph displays historical data for, by entering the period to display (in minutes).
• If you are running a cluster of web servers on different machines you can specify which web server to monitor by selecting the web server from the drop down list.
After you change any of these fields, click the Change monitoring configura-tion button for the changes to take effect.
4.4 Using the Traffic History Pages
The traffic history pages are useful for viewing recent activity across your web server system. They enable you to view graphs of traffic, analyzed over the last week or 24 hour period.
The pages enable you to view traffic history in the following ways: • Traffic Overview — This page enables you to view the total traffic on
specific web servers (on different machines), Virtual Servers or Subservers. • Website Comparison — This page enables you to compare the traffic on
your busiest websites.
• Cluster Traffic Analysis — This page enables you to compare the traffic on the web server machines in your cluster20.
Using the Traffic Overview Page
Use the traffic overview page to view the total traffic on web server machines, Virtual Servers or host headers. Access the page by clicking the Traffic Over-view link in the Web Controller menu.
20. Normally a machine in a cluster runs just one web server although it can run more, as described in the Zeus Web Server User Guide.
The page displays a graph of total traffic in either hits per minute or bytes per second over the last week or 24 hour period. The total is calculated by adding together the traffic on the machines, Virtual Servers and host headers that you specify.
Select which information to plot, in the following way:
• Select whether you want to view a total of traffic on all web servers on all machines in your cluster, or just one web server. If you only want to see traffic for one web server machine, select it in the drop down list. • Select whether you want to view a total of traffic on all running Virtual
Servers, or just one of them. If you only want to see traffic for one Virtual Server, select it in the drop down list.
• Select whether you want to view a total of traffic on all host headers, or just one of them. If you only want to see traffic for one host header, click the This host header radio button, then enter the host header name. If you selected an individual Virtual Server in the previous step, the host header you enter must be running on that Virtual Server, otherwise no results will be displayed.
Select how the traffic overview should be displayed, as follows:
• Specify whether to view hits per minute or bytes per second, by selecting either from the drop down list.
• Specify whether to view statistics for the previous 24 hours, or previous week, by selecting the value from the drop down list.
Click the Plot button for the changes to take effect.
Using the Website Comparison Page
Use the website comparison page to compare the traffic on your busiest websites. Access the page by clicking the Website Comparison link in the Web Controller menu.
The page displays a graph of traffic on your busiest websites (or host headers), using a different colored line for each of them. The traffic can be displayed in either hits per minute or bytes per second over the last week or 24 hour period.
