Applies To:

Show Versions Show Versions

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

This chapter provides the information that you need to perform the initial configuration and subsequent maintenance for the WebAccelerator system. These tasks include:
Essential configuration tasks
You must perform these configuration tasks before the WebAccelerator system can accelerate traffic for your applications.
Optional configuration tasks
You can perform these additional configuration tasks to fine-tune and customize the WebAccelerator system’s configuration and to deploy multiple WebAccelerator systems in different locations, in a symmetrical configuration.
Maintenance tasks
You perform these maintenance tasks periodically, after you complete the initial configuration.
The following essential configuration tasks are required for the WebAccelerator system to start accelerating traffic. These tasks include:
Initial configuration for the BIG-IP Local Traffic Manager
To initiate the configuration process, you must first configure the general network settings on the BIG-IP Local Traffic Manager, install the WebAccelerator system’s license, and enable it.
Initial configuration for the WebAccelerator system
To start the configuration process for the Webaccelerator system, you must perform the following tasks:
Configure a Network Time Protocol (NTP) server
For the WebAccelerator system to properly maintain its cache, as well as synchronize configuration changes for symmetrical deployments, you must ensure that the time on the origin servers and the time on the WebAccelerator system(s) are the same, by configuring a NTP server.
Enable the http-acceleration profile
The http-acceleration profile classifies traffic using HTTP header, cookie, host, path, and other HTTP items. You must enable and use this profile for optimal http traffic management performance.
Define a virtual server and pool associated with the WebAccelerator-enabled HTTP class profile on the BIG-IP Local Traffic Manager
The virtual server load balances pools that host the web application that you are accelerating. You configure the virtual server and one or more pools.
Create an application profile on the WebAccelerator system
An application profile provides key information that the WebAccelerator system uses to appropriately handle requests to the associated applications. You must create an application profile for each application that clients are accessing.
Before you configure the WebAccelerator system, you must perform the following configuration tasks on the BIG-IP Local Traffic Manager.
If you have not yet completed the required configuration on the BIG-IP Local Traffic Manager, refer to the Installation, Licensing, and Upgrades for BIG-IP® Systems guide, and the BIG-IP® Network and System Management Guide for additional information. Both of these guides are available on the Technical Support web site, http://tech.f5.com.
After you perform these configuration tasks on the BIG-IP Local Traffic Manager, you must enable the WebAccelerator system.
Important: On the WebAccelerator 4500 platform, the WebAccelerator system is enabled by default; therefore, the following procedure is not required. However, on the WebAccelerator 4500 platform only, you must issue the bigstart restart command from the command line after you perform the initial Setup utility procedures, to restart the daemons and access the WebAccelerator system’s navigation menu.
1.
On the Main tab of the navigation pane, expand System and click License.
The License screen opens.
2.
Click the Modules tab.
3.
From the WebAccelerator list, select Enabled and click the Update button.
The screen refreshes with a prompt to reboot the system.
4.
Reboot the system from the menu on the appliance’s LCD panel.
Optionally, you can reboot by establishing an SSH session on the management port, and typing the following command:
After you have performed the initial configuration tasks on the BIG-IP Local Traffic Manager, you can begin configuration for the WebAccelerator system, by:
The first task you need to perform to configure the WebAccelerator system is to define a Network Time Protocol (NTP) server. NTP is a protocol that synchronizes the clocks on your network with a defined NTP server. This synchronization ensures that the WebAccelerator system properly maintains its cache, and synchronizes configuration changes for optional symmetrical deployments.
1.
On the Main tab of the navigation pane, expand System and click General Properties.
The General Properties screen displays.
2.
From the Device menu, choose NTP.
The NTP Properties screen displays.
3.
In the Address box, type an address for the NTP server.
4.
Click the Add button.
The IP address appears in the Time Server List.
5.
Click Update.
The second task you need to perform to configure the WebAccelerator system is to create an HTTP class profile with the WebAccelerator system enabled. The HTTP class profile uses the HTTP header, cookie, host, and path, and other HTTP items to classify traffic in order to accelerate traffic for applications that are running on a virtual server.
1.
On the Main tab of the navigation pane, expand WebAccelerator and click Applications.
The Applications screen displays in a new window.
2.
On the Main tab of the navigation pane, click Classes.
The HTTP Class Profile screen opens.
3.
Click the Create button.
The New HTTP Class Profile screen opens.
4.
In the Name box, type a user-defined name for the HTTP class profile.
For example, SEAWebAccelerator.
5.
From the Parent Profile list, select httpclass.
6.
In the Configuration section, verify that WebAccelerator system is set to Enabled. Leave all other settings at Match all.
7.
Click the Finished button.
The system adds the new HTTP class profile and displays the HTTP Class Profiles screen.
Important: The HTTP class profile exists in both the WebAccelerator and the Local Traffic sections of the Configuration utility. The difference between the two is that in the WebAccelerator section of the Configuration utility, the WebAccelerator system is enabled by default. In the Local Traffic section of the Configuration utility, you must check the Custom check box and explicitly enable WebAccelerator. If you create the HTTP class profile from the Local Traffic section and you do not enable the WebAccelerator system, you effectively disable web acceleration for the associated virtual server.
The third task you need to perform to configure the WebAccelerator system is to define a virtual server and pool, and associate the HTTP class profile that you created in the previous step. The virtual server processes and routes incoming traffic in accordance with the settings that you configure in the associated HTTP class profile. The pool hosts the actual web application content that you want the WebAccelerator system to accelerate with the application profile policy.
Note: The following procedure outlines only the basic virtual server and pool configuration. For detailed information about virtual servers, pools, and the other local traffic components, refer to the Configuration Guide for BIG-IP® Local Traffic Management on the AskF5 Technical Support web site, http://tech.f5.com.
1.
On the Main tab of the navigation pane, expand Local Traffic, and then click Virtual Servers.
The Virtual Servers list screen displays.
2.
Click the Create button.
The New Virtual Server screen displays.
3.
In the Name box, type a name for the virtual server.
4.
For the Destination Type, click the Host button and type an IP address in the Address box.
5.
In the Service Port box, type the appropriate service port for your application. For example, for HTTP, the port is 80. Alternatively, you can select a service type from the list.
6.
Select Enabled from the State list.
7.
In the Configuration section, select http-acceleration from the HTTP Profile list.
8.
In the Resources section, select the WebAccelerator-enabled HTTP class profile that you created from the HTTP Class Profiles Available list, and click the Move button (<<) to add the profile to the Enabled list.
9.
Next to the Default Pool list, click the Add (+) button.
The New Pool screen opens.
10.
In the Name box, type a name for the pool.
11.
For Health Monitors, select http from the Available list and click the Move button (<<) to add the monitor to the Active list.
12.
In the Resources section, select a Load Balancing Method from the list.
13.
Leave Priority Group Activation set to Disabled.
14.
Into the Address and Port boxes, type the address and port for the pool members.
15.
Click the Add button.
16.
Click Finished.
The screen refreshes and opens the New Virtual Server screen, where you see the new pool in the Default Pool list.
17.
Click Finished again.
The system updates the configuration, and the Virtual Server list screen displays and you can see the virtual server that you created.
After you create the HTTP class profile and configure the virtual server and pool, you configure the applications that you want the WebAccelerator system to accelerate. You start this process by creating an application profile. The application profile provides the key information that the WebAccelerator system needs to appropriately handle requests to your site’s web applications. When configuring an application profile, you specify an associated acceleration policy and define a host map.
Note: For more information about pre-defined and user-defined acceleration policies, see the Policy Management Guide for the BIG-IP® WebAccelerator System.
To begin the process of creating an application profile, you must first decide which acceleration policy you want to use. If you want to use a general, non-vendor specific policy, you may choose to use one of the two pre-defined general delivery acceleration policies. Both work well for most sites that use Java 2 Platform Enterprise Edition (J2EE) applications.
Level 1 Delivery
This pre-defined acceleration policy is compliant with HTML version 2.0. For this acceleration policy, the WebAccelerator system:
Ignores any no-cache directives included in HTTP Cache-Control response headers, and uses the cache response directives that it receives from the origin web server.
Level 2 Delivery
This pre-defined acceleration policy is compliant with HTML version 3.0 and later. For this acceleration policy, the WebAccelerator system:
Caches HTML pages and assigns a lifetime setting of 0, which prompts the WebAccelerator system to provide fresh content by making subsequent requests for that content, using a conditional GET.
Ignores any no-cache directives included in HTTP Cache-Control response header, and uses the cache response directives that it receives from the origin web server.
You may also choose to create a new, user-defined acceleration policy to assign to your application. If you want to use this option, F5 Networks recommends that you start with a pre-defined policy and edit it as required, to suit your site’s specific needs. For information about specific acceleration policy features and instructions about how to create user-defined acceleration policies, see the Policy Management Guide for the BIG-IP® WebAccelerator System.
When a browser sends an HTTP request to the WebAccelerator system, the WebAccelerator system compares the host on the request to those in its host map to determine which application and associated application policy to use 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.
Note: The WebAccelerator system is also capable of managing requests for unmapped domains, which are called unmapped requests. For more information, see Processing unmapped requests.
*.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.
1.
On the Main tab of the navigation pane, expand WebAccelerator and click Applications.
The Applications screen displays in a new window.
2.
Click the Create button.
The New Application screen opens.
3.
In the Application Name box, type a name for the application.
4.
In the Description box, type an optional description.
5.
From the Central Policy list, select a pre-defined or user-defined acceleration policy. For information about creating user-defined acceleration policies, see the Policy Management Guide for the BIG-IP® WebAccelerator System.
6.
From the Remote Policy list, select a pre-defined or user-defined acceleration policy. Note that this setting is applicable only for a symmetrical deployment. If you do not have a symmetrical deployment, do not select a remote policy. For more information, see Deploying a symmetrical configuration.
7.
Optionally, from the Destination Host list, select a user-defined destination host. Note that this setting displays only if you have configured an additional destination host.
8.
In the Hosts section at the bottom of the screen, click the Add Host button.
The screen refreshes and displays a Requested Host box.
9.
In the Requested Host box, type a valid host name for each client host that you want to allow access to the application.
10.
Click the Save button.
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.
1.
On a machine separate from the WebAccelerator system, and from which you can run a web browser, open the /etc/hosts file and add the host name that you used to access the web site application. The host name must point to the IP address for the virtual server that you configured.
Note: On Microsoft® Windows® 2000 and Windows® XP machines, the /etc/hosts file is located at c:\WINNT\system32\drivers\etc\hosts
For example, if you can access the web site at the www.siterequest.com domain and the virtual server is at IP address 11.1.11.3, add the following line to the /etc/hosts file on the machine running the browser to:
All network traffic from the web browser machine for www.siterequest.com subsequently goes to the virtual server.
You should see the page that you would have received if your browser had accessed the origin web servers directly. If the browser times out the request, it means that either the WebAccelerator system is not running, or the firewall is blocking access to port 80 on the WebAccelerator system.
3.
If you receive an Access denied by intermediary error, perform the following tasks:
Verify that the /etc/hosts file is correct.
Verify that you used a domain in the request that matches a requested host in the host map, and that it maps to the destination host.
Note: In addition to the optional configuration tasks noted here, you can also create a user-defined acceleration policy. For more information, refer to the Policy Management Guide for the BIG-IP® WebAcceleratorSystem.
A request for a domain that is not listed in the requested host map is called an unmapped request. If you create an application policy that is based on a host name that is not identified in a host map, you will have an unmapped host map. By default, the WebAccelerator system replies to clients that request unmapped hosts with an HTTP 403 response code. F5 Networks recommends that you reconcile unmapped requests by adding the host name to the host map for the applications that are using the specified application profile.
Another option is to allow the WebAccelerator system to process unmapped requests, instead of responding with an error; however, the following security implication is associated with processing unmapped requests.
If you configure the WebAccelerator system to process unmapped requests and you do not specify a proxy server, you enable the WebAccelerator system to act as a relay. F5 Networks recommends that you do not enable unmapped request processing unless your network meets one of the following conditions.
You specify a proxy server to forward the unmapped requests to, as described in step 5 of the following procedure, and you configure that proxy server to properly manage unwanted or unsanctioned requests.
1.
On the Main tab of the navigation pane, expand WebAccelerator and click Applications.
The Applications screen displays in a new window.
2.
In the navigation pane, click Unmapped hosts.
The Unmapped Hosts screen opens.
3.
Check the box next to Process requests for unmapped hosts.
The screen refreshes and displays additional options.
4.
From the Policy list in the Policy Options section, select an application policy for which you want to process unmapped requests.
5.
To forward unmapped host requests to a specific proxy server, select the button next to Forward unmapped host requests to a proxy server in the Forward Proxy Options section, and type an address in the Server Address box.
6.
In the Connection Properties section, for Protocol Security, select the button next to one of the following choices:
Same as Original Request
When this option is selected, the WebAccelerator system uses the same protocol to send data to and receive data from the origin web servers, as is used for the client request.
HTTP only
When this option is selected, the WebAccelerator system uses only HTTP for sending and receiving data, even if HTTPS is used for the original request. Use this option only if the WebAccelerator system and origin web servers are on the same protected network and you want to avoid the overhead of HTTPS connections.
7.
In the Connection Timeout box, type the number of seconds that the WebAccelerator system should wait to establish a connection.
8.
In the Read/Write Timeout box, type the number of seconds that you want the WebAccelerator system to wait for a read or write operation to the origin web servers to complete. Once the WebAccelerator system reaches this limit, the operation times out.
9.
In the Retries box, type the number of times the WebAccelerator system should attempt to connect to the origin web servers, in the event of a connection failure.
10.
In the Lifetime box, type a number, and select minutes or seconds from the associated menu, to specify the amount of time that the WebAccelerator system should hold a persistent connection open to the origin web servers.
Each time the WebAccelerator system requests and receives data from the origin web servers, it checks to see if the connection has been open for a period of time that is longer than defined for this field. If it has been, the WebAccelerator system drops the connection and reconnects to the origin web server before attempting to request data.
11.
Click the Save button.
In most cases, the default settings are efficient for the destination host that you define for the origin web servers. You can, however, fine-tune your configuration by changing connection and timeout values, after you initially configure your host map. If you change destination host values, you must recheck the configuration as described in the section titled, Verifying the application profile.
1.
On the Main tab of the navigation pane, expand WebAccelerator, and then click Applications.
The Applications screen displays in a new window.
2.
From the Configuration menu, click Destination Hosts.
The Destination Hosts screen opens with a list of configured destination hosts.
3.
Click the name of the destination host that you want to modify.
The destination host’s options display.
4.
In the Connections Properties section, for Protocol Security, select the button next to one of the options:
Same as Original Request
When this option is selected, specifies that the WebAccelerator system uses the same protocol to request data from the origin web servers, as is used for the client request.
HTTP only
When this option is selected, specifies that the WebAccelerator system uses only HTTP for sending and receiving data, even if HTTPS is used for the original request. Use this option only if the WebAccelerator system and origin web servers are on the same protected network, and you want to avoid the overhead of HTTPS connections.
5.
In the Connection Timeout box, type the number of seconds that you want the WebAccelerator system to wait for a response from the origin web servers, when requesting content.
6.
In the Read/Write Timeout box, type the number of seconds that you want the WebAccelerator system to wait for a read or write operation to the origin web servers to complete. Once the WebAccelerator system reaches this limit, the operation times out.
7.
In the Retries box, type the number of times the WebAccelerator system should attempt to connect to the origin web servers, in the event of a connection failure.
8.
In the Lifetime box, type a number, and select minutes or seconds from the associated menu, to specify the amount of time that the WebAccelerator system should hold a persistent connection open to the origin web servers.
Each time the WebAccelerator system requests information from the origin web server, it checks to see if the connection has been open for a period of time that is longer than defined for this field. If it has been, the WebAccelerator system drops the connection and reconnects to the origin web server before attempting to retrieve the requested data.
9.
Click the Save button.
Most browsers create a limited number of persistent TCP connections when requesting data. You can achieve faster data downloads by using the WebAccelerator system’s MultiConnect feature, which modifies embedded URLs with unique subdomains, prompting the browser to open more persistent TCP connections (up to two per subdomain generated by the WebAccelerator system).
When MultiConnect is enabled, it prompts the client’s web browser to open up to four persistent 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.
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 low-latency, high-bandwidth links, because the additional TCP connections also increases the amount of traffic your site has to handle.
Image tags:
<img src=”...”>
Script tags:
<script src=”...”>
Forms whose input type is an image:
<form><input type=”image” src=”...”></form>
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.
Once configured, the WebAccelerator system changes the domain on qualifying embedded URLs and links to use the domains you specified. For example:
1.
On the Main tab of the navigation pane, expand WebAccelerator and click Applications.
The Applications screen displays in a new window.
2.
Click the name of the application for which you want to configure the MultiConnect feature.
The Edit Applications screen opens.
3.
In the Hosts section at the bottom of the screen, click the Options link next to the Requested Host box for which you want to configure MultiConnect.
The screen refreshes and displays the MultiConnect options.
4.
From the HTTP Subdomains and HTTPS Subdomains lists, select the number of subdomains that you want the WebAccelerator system to generate for each protocol.
5.
In the Subdomain Prefix box, type a prefix or leave it at the default of wa.
6.
Click the Save button.
Once you map the additional subdomains, you can enable the MultiConnect feature for a specific acceleration policies as described in Chapter 8 Assembly rules, of the Policy Management Guide for the BIG-IP® WebAccelerator System.
An optional deployment for a site with multiple WebAccelerator systems is a symmetrical configuration. A symmetrical configuration consists of central and remote WebAccelerator systems that have synchronized configurations. With this configuration, users can transparently utilize the functionality of a WebAccelerator system on another network across town, or across the globe, from both sides of the transaction.
In a symmetrical configuration, the central WebAccelerator system is the WebAccelerator system that is closest to the application it is accelerating. The central WebAccelerator system is accessed by local clients as well as clients from a remote WebAccelerator system located in a separate geographic location, which can be across the office or across the country.
For example, say you have a WebAccelerator system located at a corporate office in North America that is accelerating a web mail server application that employees in a satellite office in Europe access. For this symmetrical configuration, the central WebAccelerator system is located at the corporate office, closest to the web mail application, and the remote WebAccelerator system is the WebAccelerator system in Europe.
In this example, the satellite office employee sends an email request to his local WebAccelerator system in Europe, which responds to the request, or, if new content is required, sends the request to the central WebAccelerator system located in the corporate office in North America. The central WebAccelerator system responds to the request, or, if new content is required, sends the request to the origin web mail server. The central WebAccelerator system then caches the response and responds to the remote WebAccelerator system in Europe.
Once the remote WebAccelerator system in Europe receives the response from the central WebAccelerator system in North America, it caches that response and then sends it to the employee. As long as the content is still valid, the remote WebAccelerator system in Europe can then respond to future requests for the same content from local clients.
You create a symmetrical configuration, by first configuring the central WebAccelerator systems and then adding the remote WebAccelerator systems. After creating the symmetrical configuration on one WebAccelerator system, you manually synchronize the deployment from each WebAccelerator system in the deployment, to propagate the configuration.
All members of a symmetrical configuration are peers. Therefore, after you perform the initial configuration and manually synchronize the systems, subsequent changes that you make to any member propagate immediately to all other members of the symmetrical configuration. This propagation happens regardless as to whether the member you made a change to, is a central or remote WebAccelerator system.
Keep in mind that you must have at least one designated central WebAccelerator system at all times. In other words, you cannot delete or change the role of a central WebAccelerator system unless you have another central WebAccelerator system configured.
Note: When configuring a symmetrical deployment, the IP addresses that you use for the central and remote WebAccelerator systems must be external facing self IP addresses. To find the external facing self IP address for each WebAccelerator system, use the b self command.
1.
On the Main tab of the navigation pane, expand WebAccelerator, and then click Applications.
The Applications screen displays in a new window.
2.
On the Main tab of the navigation pane in the new window, click WebAccelerators.
The WebAccelerators screen displays.
3.
Click the Create button.
The New WebAccelerator screen displays.
4.
In the Name box, type a name for the central WebAccelerator system.
5.
If the WebAccelerator system you are configuring uses network address translation (NAT) to communicate with other WebAccelerator systems in the data center, click the Use NAT Support box.
The screen refreshes to display additional options.

If the WebAccelerator system you are configuring does not use NAT, skip to step 8.
6.
In the Global Address box, type the public IP address that the WebAccelerator system uses to communicate with computers outside of the data center.
7.
In the Internal Address box, type the IP address that the WebAccelerator system uses to communicate with other WebAccelerator systems within the data center. Skip to step 9.
8.
In the IP Address box, type the static self IP address for the central WebAccelerator system. This is the external facing (non-floating) self IP address for the central system.
9.
Click the Central button.
10.
From the Data Center list, select a Data Center or leave it at the Default Data Center.

Alternatively, select Add a New Data Center and type a new data center name in the associated box.
11.
Click the Save button.
1.
Click the Create button.
The New WebAccelerator screen displays.
2.
In the Name box, type a name for the remote WebAccelerator system.
3.
If the WebAccelerator system you are configuring uses network address translation (NAT) to communicate with other WebAccelerator systems in the data center, click the Use NAT Support box.
The screen refreshes to display additional options.

If the WebAccelerator system you are configuring does not use NAT, skip to step 6.
4.
In the Global Address box, type the public IP address that the WebAccelerator system uses to communicate with computers outside of the data center.
5.
In the Internal Address box, type the IP address that the WebAccelerator system uses to communicate with other WebAccelerator systems within the data center. Skip to step 7.
6.
In the IP address box, type the static self IP address for the remote WebAccelerator system. This is the external facing (non-floating) self IP address for the remote system.
7.
Click the Remote button.
8.
From the Data Center list, select a Data Center or leave it at Default Data Center.

Alternatively, select Add a New Data Center and type a new data center name in the associated box.
9.
Click the Save button.
1.
On the Main tab of the navigation pane, expand WebAccelerator, and then click Applications.
The Applications screen displays in a new window.
2.
On the Main tab of the navigation pane in the new window, click WebAccelerators.
The WebAccelerators screen displays.
3.
Click the name of a WebAccelerator system to view or change its configuration details.
The Edit WebAccelerator screen displays.
4.
Click the Save button to save any changes you made, or click the Cancel button to return to the WebAccelerators screen.
After you configure the central and remote WebAccelerators on one WebAccelerator system, you must perform a manual synchronization by logging on to all the other WebAccelerator systems in the deployment, and running a synchronization script on each machine. This manual synchronization is required only upon initial configuration, or any time that you add a new WebAccelerator system to the symmetrical configuration.
1.
From the command line of each remote WebAccelerator system in the symmetrical configuration, type the following command:
2.
Type Y.
The system prompts you to type the self IP address of the WebAccelerator system on which you performed the initial symmetrical deployment configuration.
3.
Type the self IP address as directed, and press Enter.
The system prompts you to enter the system’s root password.
4.
Type the password and press enter.
The WebAccelerator system confirms that it successfully received and loaded the configuration files. You can now view the symmetrical configuration from the Configuration utility.
After you have configured the WebAccelerator system, and are processing traffic, you can perform the following maintenance 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 system’s initial installation process and configuration, you can perform additional checks to verify that the software is working correctly and that you selected and correctly configured your initial application policies and host maps.
pvac
waicd
You can monitor the WebAccelerator system’s performance by viewing graphs and tables from the Performance Reports screen. The Performance Reports include information about page requests, the frequency of those requests, and how well the WebAccelerator system serviced those requests from its cache. You can use this information to evaluate your acceleration policies, adjusting them as required to maximize performance for your site.
By using Performance Reports, you can monitor how the WebAccelerator system is processing requests, and use this information to effectively manage your applications.
Traffic Reports
Displays the number of requests (hits) received, and responses served, by the WebAccelerator system.
Bytes Reports
Displays the bytes of content that the WebAccelerator system has sent in response to requests.
Response Reports
Displays the average amount of time it takes the WebAccelerator system to respond to a request from the client.
The WebAccelerator system also provides you with an option to save Performing Reports to a specified file type so that you can import them into specific applications.
1.
On the Main tab of the navigation pane, expand WebAccelerator, and then click Applications.
The Applications screen displays in a new window.
2.
On the Main tab, expand Performance Report and click Traffic Reports, Bytes Reports, or Response Reports.
Time: Provides data in the following increments:
- 5 minutes
- Hourly
- Daily
Transaction Type: Provides data based on transaction type.
Content: Provides data based on the following two content options:

- by Content Type: Provides data based on content type as defined in the globalfragment.xml file.
- by Content Size: Provides data based on the size of the response.
HTTP Status: Provides data based on HTTP status.
1.
On the Main tab of the navigation pane, expand WebAccelerator, and then click Applications.
The Applications screen displays in a new window.
2.
On the Main tab, expand Performance Report and click Traffic Reports, Bytes Reports, or Response Reports.
3.
Click the Edit Filter button.
5.
Click the Update button to save the changes.
Note: The Performance Reports display content according to the parameters that you select for the filter. Any changes that you make to the filter values stay in effect for all reports, until you change them.
1.
From any performance report screen, select one of the following export options, located at the bottom of the screen:
CSV
Excel
XML
2.
Click the Save button.
The WebAccelerator system manages system log files that contain large amounts of data. By default, the WebAccelerator system monitors these logs every hour and rotates the file any time the size is over 10 MB. This log file rotation helps to avoid filling up the disk partition, which could potentially cause a system failure.
You can change the interval at which the WebAccelerator system monitors the system logs from hourly to daily, by issuing the following two Linux shell commands: 

rm /etc/cron.hourly/wa_logrotate

ln –s /usr/local/wa/scripts/wa_logrotate /etc/cron.daily/wa_logrotate/

 

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)