The Web Transaction (PI_WT) record stores information about a Web transaction service response time. This is a multi-instance record. Each scope becomes an instance.

Item	Default value	Changeable
Collection Interval	360	Y
Collection Offset	0	Y
Log	No	Y
LOGIF	(Blank)	Y

PI_WT_MSR_COND_ID, PI_WT_SCOPE_NAME

None

• Fixed part: 681 bytes
• Variable part: 392 bytes

View name (Manager name)	Description	Summary rule	Format	Delta	Data source
Data Transfer Time (DATA_TRANS_TIME)	Data transfer time (seconds)	AVG	double	No	Probe Daemon
DNS Time (DNS_TIME)	DNS time (seconds)	AVG	double	No	Probe Daemon
HTTP Time (HTTP_TIME)	HTTP time (seconds)	AVG	double	No	Probe Daemon
Request Count (REQ_COUNT)	Number of requests (count)	AVG	double	No	Probe Daemon
Scope Name (SCOPE_NAME)	Scope name. For the overall transaction, ALL is set. For a scope name, scope N is set (N: 1 to 8).	COPY	string (up to 31 bytes)	No	Probe Daemon
Server Processing Time (SERV_PROCESS_TIME)	Server processing time (seconds)	AVG	double	No	Probe Daemon
Setup Time (SETUP_TIME)	Setup time (seconds)	AVG	double	No	Probe Daemon
TCP Connection Time (TCP_CON_TIME)	TCP connection time (seconds)	AVG	double	No	Probe Daemon
Throughput (THROUGHPUT)	Throughput (bits/second)	AVG	double	No	Probe Daemon
Total Amount of Data (TOTAL_DATA_SIZE)	Total amount of data (bytes)	AVG	double	No	Probe Daemon
Total Resource Size (TOTAL_RES_SIZE)	Total size of resource (bytes)	AVG	double	No	Probe Daemon
Total Response Time (TOTAL_RESP_TIME)	Total response time (seconds)	AVG	double	No	Probe Daemon

A Web transaction probe performs not only a measurement consisting of a single set of a request and a response but also a measurement in which a series of HTTP(S) requests and responses constitute a single Web transaction.

A Web transaction's measurement result covers the playback of the entire Web transaction. A measurement result is also output for each specified scope (any page transactions) in the same manner.

The Web transaction probe plays back the information defined in the Web transaction file according to the measurement condition. A specified URL's response is checked according to the response determination information defined in the Web transaction file. Any measurement that does not meet the condition results is a measurement failure. The checking based on the response determination information is applicable only when the response acquired from the specified URL is in HTML format (Content-Type is text/html). If the received data is compressed, the response check results in a measurement failure. This checking is not performed for acquisition of embedded resources.

The following describes and provides notes on a Web transaction operating environment.

• Acquisition is made for each HTML frame.
• Programs, such as plug-ins and Java Scripts, are downloaded but not executed.
• With respect to acquisition of embedded resources, if the Web transaction is defined to acquire embedded resources, they are acquired automatically during measurement. The Web transaction analyzes the HTML acquired during measurement (only when the received data is not compressed), and acquires the resources specified in the values of the tags and attributes listed in the table below.
• Note that the tag and attribute names are not case sensitive.
  

  Table 9-18 Embedded resources and frames to be acquired

  Tag name	Attribute name
  applet	code
  body	background
  embed	src
  img	src
  object	data
  script	src

• A Web transaction does not acquire a resource embedded in a page that is created dynamically by a program such as JavaScript.
• For a cookie that is generated (received) during measurement, the Web transaction performs measurement accordingly. Therefore, unless this is necessary for other reasons, there is no need to specify cookies in the Web transaction file. Cookies that are specified in the Web transaction file are sent together with the cookies generated (received) during measurement.
• For the user agent specified when a HTTP(S) request is issued, PFM - Agent for Service Response (Windows) is used by default.
• If a Web transaction that uses the same user name for login is defined in multiple measurement conditions, and multiple logins by the same user name are not permitted, measurement may fail. Therefore, if multiple logins by the same user name are not permitted, you must take appropriate action, such as providing a different user for measurement of each measurement condition.
• You can define a Web transaction with the same contents in multiple measurement conditions.
• For Web authentication, the Basic Authentication method is used.
• A Web transaction accepts cookies based on Netscape Communication's specifications.
• If acquisition of a Web page specified by a URL and embedded resources involves use of a proxy for only part of the acquisition target, measurement cannot be performed.
• When HTTPS is measured in a Web transaction, the supported encryption types are the same as those for the HTTPS probe. You cannot access a page protected with unsupported cipher strength. For details, see HTTPS.
• To apply server authentication and client authentication, a certificate file must be registered in the same way as for the HTTPS probe. For details, see HTTPS.

HTTP Version

HTTP/1.0 is applicable.

Referer Header

The Web transaction probe does not issue the requests with the Referer Header.

RFC compliance

• RFC1866: Hypertext Markup Language - 2.0
• RFC2616: Hypertext Transfer Protocol - HTTP/1.1
• RFC2396: Uniform Resource Identifiers (URI): Generic Syntax
• RFC2818: HTTP over TLS

For the functions that are not compliance with RFCs and the restrictions, see the above notes.

HTTP(S) processing sequence

For details about a sequence of HTTP(S) communication processing performed in a Web transaction, see HTTP (PI_HTP) and HTTPS (PI_HTPS) in this chapter.