Which parameter(s) need to be specified in order for AppResponse WTA to perform user tracking?

To perform user tracking, AppResponse Web Transaction Analysis (WTA) requires a complete definition of both the application and the tracking method. First, the web application must be defined by its Server IPs and Server Ports so AppResponse knows which traffic to analyze. Second, a user identification rule must be configured for that application. This rule specifies the User Key or Session Key (e.g., a cookie name like JSESSIONID or a URL parameter) used to uniquely identify a user's session, and a URL Pattern to define the specific pages where this key should be extracted. All these parameters are essential for the feature to function correctly.

A. Username, Server Ports and Server IPs

"Username" is the result or output of a successful user tracking configuration, not an input parameter used to configure it.

C. Session Key and URL Pattern

This is incomplete. While these parameters define the tracking rule, they are useless without specifying the application (via Server IPs and Ports) to which the rule applies.

D. Web Application, Server Ports and Server Ips

This only defines the application traffic to be monitored. It does not configure the specific mechanism required to identify and track individual user sessions.

1. Riverbed AppResponse User's Guide, Version 11.12.1, Chapter 6: "Web Application Analysis Configuration", Page 118, Section: "Configure web applications". This section details the requirement to define a web application using its Server IP addresses and Server TCP ports as the foundational step.

2. Riverbed AppResponse User's Guide, Version 11.12.1, Chapter 6: "Web Application Analysis Configuration", Page 125, Section: "Configure user identification". This section explicitly states: "A user identification rule consists of a source, a key, and a URL pattern." This "key" corresponds to the User Key or Session Key, and it is configured within a specific web application. This confirms that both the application definition (IPs/Ports) and the identification rule (Key, URL Pattern) are required.