2.1.3 Web transaction measurement test

With PFM - Agent for Service Response, a predefined Web transaction measurement test can be executed.

Executing the measurement test command (jpcvtest) enables you to issue an HTTP(S) request according to the Web transaction definition and receive standard output that indicates whether a response to the request can be obtained. For details, see jpcvtest (executes measurement tests) in 11. Commands.

The following figure shows an overview of a Web transaction measurement test.

Figure 2‒6: Overview of a Web transaction measurement test

The measurement test command (jpcvtest) reads the following probe action condition definition file. The contents and creation method of the definition for the Web transaction to be measured are the same as those described in 2.1.2 Measurement of Web transactions.

• Probe action condition definition file (esp.conf)

  This file defines startup options of PFM - Agent for Service Response. The following options are read and used when a Web transaction is measured with the measurement test command (jpcvtest).

  Table 2‒4: Probe action condition definition file used by the measurement test command "jpcvtest"

  Section name	Key name
  General	mode
  	disable_ssl_protocol
  	html_script_skip_flag
  	enable_low_level_ssl_protocol
  WEBTRANS Probe	max_keep_alive_session
  	skip_emb_rsc_error
  	post_redirect_method
  Cluster	cluster_flag
  	shared_directory

  For details, see 8.2 Probe action condition definition file (esp.conf).

• Measurement condition registration file (esptask.xml)

  This file defines the measurement conditions, such as a target's service type, host name, and measurement interval. You define the measurement conditions in PFM - Web Console (or you can define conditions by editing the measurement condition registration file directly).

  The definition for the Web transaction that undergoes a measurement test is read from this file.

  For details about defining conditions in PFM - Web Console, see 4.7 Defining measurement conditions in PFM - Web Console. For details about measurement condition registration file, see 8.3 Measurement condition registration file (esptask.xml).

• Web transaction file

  This file defines information such as a target Web transaction's access destination URL, Web authentication, and proxy. For details, see 8.5 Web transaction files.

• Password file (esp.pdb)

  This file registers and manages the passwords needed to log on to a target Internet service. For details, see 4.3.1 Registering passwords.

Web transaction measurement tests can be used in the following cases: when a new Web transaction that is created is checked before it is used for production operations, or when you need to check whether Web transactions can be measured after a monitored Web site is changed.

The following table describes measurement test usage patterns.

Table 2‒5: Measurement test usage patterns

Usage patterns			Usage example
Checking when creating a new Web transaction	This assumes a situation in which PFM - Agent for Service Response is installed or Web transactions to be monitored are added.		Checking beforehand whether Web transactions can be monitored using a new Web transaction file that has been created
Checking after changing the settings on the monitored server	This assumes a situation in which Web content has been changed.		Checking whether Web transactions can be monitored even after components such as buttons or frames on the monitored page are changed
	This assumes a situation in which server settings have been changed.	Network configuration	Checking whether Web transactions can be monitored after server settings are changed, in the same way as before server settings are changed
		Security
		Web server function settings (such as the number of simultaneous accesses)
Checking after changing the definitions for PFM - Agent for Service Response	This assumes a situation in which the definitions for the monitored Web transaction have been changed.		Checking whether Web transactions can be monitored after the definitions in the Web transaction file are changed (the destination page, or the content of page operations is changed)
	This assumes a situation in which measurement condition definitions have been changed.		Checking whether Web transactions can be measured correctly without measurement timeout after a timeout period is changed (shortened, for example)
	This assumes a situation in which the password for a Web page that requires authentication has been changed.		Checking whether the Web page can be correctly authenticated with the new password and Web transactions can be monitored
	This assumes a situation in which a certification file has been registered or replaced.		Checking whether the Web page can be correctly authenticated and Web transactions can be monitored
Checking the Web server operating status	This assumes routine and maintenance tasks for system administrators.		Checking whether the Web server enters a running state after it is restarted.

To Page Top