You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by bu...@apache.org on 2011/03/07 23:27:18 UTC
svn commit: r786642 -
/websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html
Author: buildbot
Date: Mon Mar 7 22:27:17 2011
New Revision: 786642
Log:
Staging update by buildbot
Modified:
websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html
Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/index.en.html Mon Mar 7 22:27:17 2011
@@ -36,7 +36,7 @@
<div class="main">
<div id="content">
- <p>Available Languages: [LANG]</p>
+ <p>Available Languages: (<em>LANG</em>)</p>
<h1 id="overview">Overview</h1>
<p>Apache Traffic Server⢠speeds Internet access, enhances website
performance, and delivers unprecedented web hosting capabilities.</p>
@@ -64,10 +64,12 @@ bandwidth use. Traffic Server is designe
for enterprises, Internet service providers (ISPs), backbone providers,
and large intranets by maximizing existing and available bandwidth.</p>
<h2 id="deployment-options">Traffic Server Deployment Options</h2>
-<p>To best suit your needs, Traffic Server can be deployed in several ways:
-<em> As a web proxy cache
-</em> As a reverse proxy
-* In a cache hierarchy</p>
+<p>To best suit your needs, Traffic Server can be deployed in several ways:</p>
+<ul>
+<li>As a web proxy cache</li>
+<li>As a reverse proxy</li>
+<li>In a cache hierarchy</li>
+</ul>
<p>The following sections provide a summary of these Traffic Server
deployment options.</p>
<h3 id="web-proxy-cache">Traffic Server as a Web Proxy Cache</h3>
@@ -132,12 +134,14 @@ for detailed information, refer to
entries of origin servers to which Traffic Server connects to fulfill
user requests. This information is used to adapt future protocol
interactions and optimize performance. Along with other information,
-the host database tracks:
-<em> DNS information (for fast conversion of hostnames to IP addresses)
-</em> The HTTP version of each host (so advanced protocol features can be
- used with hosts running modern servers)
-* Host reliability and availability information (so users will not
- wait for servers that are not running)</p>
+the host database tracks:</p>
+<ul>
+<li>DNS information (for fast conversion of hostnames to IP addresses)</li>
+<li>The HTTP version of each host (so advanced protocol features can be
+ used with hosts running modern servers)</li>
+<li>Host reliability and availability information (so users will not
+ wait for servers that are not running)</li>
+</ul>
<h3 id="dns-resolver">The DNS Resolver</h3>
<p>Traffic Server includes a fast, asynchronous DNS resolver to streamline
conversion of hostnames to IP addresses. Traffic Server implements the
@@ -148,12 +152,13 @@ popular bindings in memory, DNS traffic
<h3 id="traffic_server_processes_">Traffic Server Processes ###</h3>
<p>Traffic Server contains three processes that work together to serve
Traffic Server requests and manage/control/monitor the health of the
-Traffic Server system. The three processes are described below:
-<em> The traffic_server process is the transaction processing engine of
+Traffic Server system. The three processes are described below:</p>
+<ul>
+<li>The traffic_server process is the transaction processing engine of
Traffic Server. It is responsible for accepting connections,
processing protocol requests, and serving documents from the cache
- or origin server.
-</em> The traffic_manager process is the command and control facility of
+ or origin server.</li>
+<li>The traffic_manager process is the command and control facility of
the Traffic Server, responsible for launching, monitoring, and
reconfiguring the traffic_server process. The traffic_manager
process is also responsible for the proxy autoconfiguration port,
@@ -165,37 +170,41 @@ Traffic Server system. The three process
that arrive in the several seconds before full server restart are
saved in the connection queue and processed in first-come,
first-served order. This connection queueing shields users from any
- server restart downtime.
-* The traffic_cop process monitors the health of both the
+ server restart downtime.</li>
+<li>The traffic_cop process monitors the health of both the
traffic_server and traffic_manager processes. The traffic_cop
process periodically (several times each minute) queries the
traffic_server and traffic_manager process by issuing heartbeat
requests to fetch synthetic web pages. In the event of failure (if
no response is received within a timeout interval or if an
incorrect response is received), traffic_cop restarts the
- traffic_manager and traffic_server processes.</p>
+ traffic_manager and traffic_server processes.</li>
+</ul>
<p>The figure below illustrates the three Traffic Server processes.</p>
<p><img alt="Illustration of the three Traffic Server Processes" src="process.jpg" /></p>
<h3 id="admin-tools">Administration Tools</h3>
-<p>Traffic Server offers the following administration options:
-<em> The Traffic Line command-line interface is a text-based interface
+<p>Traffic Server offers the following administration options:</p>
+<ul>
+<li>The Traffic Line command-line interface is a text-based interface
from which you can monitor Traffic Server performance and network
traffic, as well as configure the Traffic Server system. From
Traffic Line, you can execute individual commands or script a
- series of commands in a shell.
-</em> The Traffic Shell command-line interface is an additional
+ series of commands in a shell.</li>
+<li>The Traffic Shell command-line interface is an additional
command-line tool that enables you to execute individual commands
- that monitor and configure the Traffic Server system.
-* Various configuration files enable you to configure Traffic Server
+ that monitor and configure the Traffic Server system.</li>
+<li>Various configuration files enable you to configure Traffic Server
through a simple file-editing and signal-handling interface. Any
changes you make through Traffic Line or Traffic Shell are
- automatically made to the configuration files as well.</p>
+ automatically made to the configuration files as well.</li>
+</ul>
<h2 id="traffic-analysis">Traffic Analysis Options</h2>
<p>Traffic Server provides several options for network traffic analysis
-and monitoring:
-<em> Traffic Line and Traffic Shell enable you to collect and process
- statistics obtained from network traffic information.
-</em> Transaction logging enables you to record information (in a log
+and monitoring:</p>
+<ul>
+<li>Traffic Line and Traffic Shell enable you to collect and process
+ statistics obtained from network traffic information.</li>
+<li>Transaction logging enables you to record information (in a log
file) about every request Traffic Server receives and every error
it detects. By analyzing the log files, you can determine how many
people used the Traffic Server cache, how much information each
@@ -208,7 +217,8 @@ and monitoring:
Squid and Netscape, and its own custom format. You can analyze the
standard format log files with off-the-shelf analysis packages. To
help with log file analysis, you can separate log files so that
- they contain information specific to protocol or hosts.</p>
+ they contain information specific to protocol or hosts.</li>
+</ul>
<p>Traffic analysis options are described in more detail in
<a href="/docs/admin/monitor">Monitoring Traffic</a>;
Traffic Server logging options are described in
@@ -217,20 +227,22 @@ Traffic Server logging options are descr
<p>Traffic Server provides numerous options that enable you to establish
secure communication between the Traffic Server system and other
computers on the network. Using the security options, you can do the
-following:
-<em> Control client access to the Traffic Server proxy cache.
-</em> Configure Traffic Server to use multiple DNS servers to match your
+following:</p>
+<ul>
+<li>Control client access to the Traffic Server proxy cache.</li>
+<li>Configure Traffic Server to use multiple DNS servers to match your
siteâs security configuration. For example, Traffic Server can use
different DNS servers, depending on whether it needs to resolve
hostnames located inside or outside a firewall. This enables you to
keep your internal network configuration secure while continuing to
- provide transparent access to external sites on the Internet.
-<em> Configure Traffic Server to verify that clients are authenticated
- before they can access content from the Traffic Server cache.
-</em> Secure connections in reverse proxy mode between a client and
+ provide transparent access to external sites on the Internet.</li>
+<li>Configure Traffic Server to verify that clients are authenticated
+ before they can access content from the Traffic Server cache.</li>
+<li>Secure connections in reverse proxy mode between a client and
Traffic Server, and Traffic Server and the origin server, using the
- SSL termination option.
-* Control access via SSL (Secure Sockets Layer).</p>
+ SSL termination option.</li>
+<li>Control access via SSL (Secure Sockets Layer).</li>
+</ul>
<p>Traffic Server security options are described in more detail in
<a href="/docs/admin/secure">Security Options</a>.</p>
</div>