Web Transaction Analysis
  
Web Transaction Analysis
Page Analysis Configuration
You enable and set up Web Transaction Analysis Module (WTA) on the Administration > Feature Settings: Web Page Analysis UI page.
Data Collection Options
Option
Notes
Enable Page Analysis
When enabled, the appliance collects web page analysis data for the specified ports and IP addresses.
Before you enable Page Analysis, mask out all private parameter values in any HTTPS traffic that might get decoded, as described in Information Privacy.
WARNING—There is no way to mask private data after it is saved on an appliance. For this reason, you must specify all sensitive parameters before you enable Page Analysis.
Ports
Collect data for the specified ports only.
Server IP Addresses
Collect data for a subset of IP addresses or select check box for all IP addresses.
Note—Collecting web page data can be highly resource-intensive, especially on very large networks with a lot of web traffic. To minimize the performance impact on the appliance, it is good practice to limit Page Analysis to ports and hosts of interest only.
Default Slow Page Threshold
The appliance uses this threshold, in seconds, to determine metrics such as Slow Pages and Slow Page Rate.
Range: 1 - 600; default is 5 seconds.
Enable SSL Decoding
When this option is selected, AppResponse 11 decodes web-over-SSL traffic on the specified ports and server IP addresses. SSL keys are managed at Administration > System Settings: SSL Decryption,
 
Unique User Definition
Configure the parameters used to identify a unique user.
GeoMap Private Data
Import a CSV file to map private IP addresses to locations.
Enable SOAP Processing
This option is useful for analyzing SOAP transactions. When this option is enabled, the appliance does the following:
◼ Translates every discrete SOAP transaction into a separate Page View (without SOAP processing enabled, a page view might include two or more SOAP transactions)
◼ Includes the SOAP method in the URLs shown for page families and individual page views in the Page Analysis insights (for example,
http://webapp.com/TradeProcess/Process.asmx [method:ProcessTrade])
Note the following:
◼ This option requires additional computing resources and might slow down performance on the appliance.
◼ Normally, you should enable this option only if your appliance is monitoring back-end SOAP traffic and not front-end browser traffic.
◼ You cannot include SOAP methods in URLs when you define web applications.