Applies To:

Show Versions Show Versions

Manual Chapter: Initial Configuration and Maintenance Tasks
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Before you configure the WebAccelerator system, you must complete the following tasks on the BIG-IP Local Traffic Manager.
Important: On the WebAccelerator 4500 platform, resource provisioning is set by default, and you simply perform the initial Setup utility procedures to access the WebAccelerator systems navigation menu.
After you have performed the initial configuration tasks on the BIG-IP Local Traffic Manager, you can begin configuration for the WebAccelerator system, by:
Network Time Protocol (NTP) synchronizes the clocks on your network with a defined NTP server. This synchronization ensures that the system properly maintains cache.
The application profile provides the key information that the WebAccelerator system needs to appropriately handle requests to your sites web applications. Before you can create the application profile, you must complete the following tasks:
When the WebAccelerator system receives an HTTP request, it compares the host on the request to those in its host map to determine which application profile to apply. Once it matches to an application profile, it can use the associated acceleration policy you assigned to handle the request.
When you create a host map, you identify the domain as it appears on the HTTP Host request header. These domains are called requested hosts. When you specify the host name for the requested host in a host map, you can use a wildcard, an asterisk (*) followed by a period, for the first character in the domain. This wildcard can represent one or more subdomains, enabling you to map several subdomains to one origin web server in one step. Using a wildcard saves time if your site has several subdomains.
*.sales.siterequest.com maps to the following (all to the same destination host):
*siterequest.com maps to the following (all to the same destination host):
*.com maps all incoming requests that end in .com to one destination host.
* maps all incoming requests to one destination host.
If the WebAccelerator system can map multiple requested host names to a request, it chooses the host name that most closely matches the request. Consider the following defined host names:
A request to www.a.com maps to www.a.com, and does not map to *.a.com.
A request to a.com maps to a.com.
Requests to c.a.com and b.a.com both map to *.a.com.
A request to c.b.a.com maps to *.b.a.com.
You may select a predefined acceleration policy that is associated with your specific application publisher or you may use one of the predefined generic acceleration policies. Both work well for most sites that use Java 2 Platform Enterprise Edition (J2EE) applications.
Generic Policy - Complete
This predefined acceleration policy is ideal for Apache HTTP servers, Internet Information Services (IIS) web servers, WebLogic application servers, and IBM Websphere Application Servers. HTML pages are cached and Intelligent Browser Referencing is enabled.
Generic Policy - Enhanced
This predefined acceleration policy is ideal for Apache HTTP servers, Internet Information Services (IIS) web servers, WebLogic application servers, and IBM Websphere Application Servers. HTML pages are cached and Intelligent Browser Referencing is enabled for includes.
Generic Policy - Extension Based
This predefined acceleration policy is ideal for High Performance policy for Ecommerce applications that uses File Extensions instead of mime-types. This application policy is ideal if response-based matching is not required.
Generic Policy - Fundamental
This predefined acceleration policy is ideal for Apache HTTP servers, Internet Information Services (IIS) web servers, WebLogic application servers, and IBM Websphere Application Servers. HTML pages are always proxied and Intelligent Browser Referencing is disabled.
The WebAccelerator system is enabled by configuring a WebAccerator application that is enabled in the Web Acceleration profile. You can enable one or more WebAccelerator applications in a Web Acceration profile.
The HTTP profile uses the HTTP Compression profile and Web Acceleration profile to classify and accelerate traffic for applications that are running on a virtual server.
The virtual server processes and routes incoming traffic in accordance with the settings that you configure in the associated Web Acceleration profile. The pool hosts the application for which you want the WebAccelerator system to accelerate traffic, using the application profiles acceleration policy.
After you create an application profile, you must verify that the WebAccelerator system is able to properly send data to and receive data from the origin web servers.
After you complete the essential configuration tasks, you can further customize by configuring the WebAccelerator system to:
Note: In addition to the optional configuration tasks noted here, you can also create a user-defined acceleration policy.
Most browsers create a limited number of TCP connections when requesting data. You can achieve faster data downloads by using the WebAccelerator systems MultiConnect feature, which modifies embedded URLs with unique subdomains, prompting the browser to open more simultaneous TCP connections.
When MultiConnect is enabled, it prompts the clients web browser to open additional TCP connections to the WebAccelerator system for each subdomain when requesting pages over the HTTP protocol. The origin web servers never get a request from these additional subdomains; the additional subdomains are used exclusively on embedded URLs or links that request images or scripts and are only for requests and/or responses between the client and the WebAccelerator system.
Image tags:
<img src=...>
Script tags:
<script src=...>
Forms whose input type is an image:
<form><input type=image src=...></form>
The MultiConnect feature is best suited for sites that have a high number of first-time visitors who are downloading a large number of images or scripts. F5 Networks recommends that you use this feature only if you have high-bandwidth links, because the additional TCP connections also increase the amount of traffic your site must manage.
Assign specific prefixes to the additional subdomains. For example, if the requested host for the mapping is www.siterequest.com, and you request two additional subdomains for the HTTP protocol, you assign a subdomain prefix of wa.
Construct a trusted SSL certificate that lists the additional subdomains that you created, as Subject Alternative Name entries. (This task is required only if you are configuring MultiConnect for use with HTTPS.)
Once you perform these tasks, the WebAccelerator system changes the domain on qualifying embedded URLs and links so that they use the domains you specified. For example:
Important: Some client browsers close HTTPS connections to one domain before opening HTTPS connections to a new domain. This type of browser behavior can decrease the speed of access to applications for which the MultiConnect feature is enabled; therefore, F5 Networks recommends that you do not enable the MultiConnect feature for HTTPS connections.
Important: If you are configuring MultiConnect for use with HTTPS, you must also construct a trusted SSL certificate that lists the additional subdomains that you created as Subject Alternative Name entries. If you are configuring MultiConnect for use with only HTTP, this step is not necessary. For more specific information about specifying Subject Alternative Name entries, contact your certificate authority.
After you map the additional subdomains and construct a trusted SSL certificate with the Subject Alternative Name entries (Subject Alternative Name entries are required only for HTTPS connections), you can enable the MultiConnect feature for a specific acceleration policy.
After you complete the basic configuration required for the WebAccelerator system to process traffic, you can perform the following procedures, as required.
The process that you use to initially configure the WebAccelerator system confirms that the basic functionality of the WebAccelerator system software is working. After you complete the WebAccelerator systems initial installation process and configuration, you can perform additional checks to verify that the software is working correctly.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)