4.7 Defining measurement conditions in PFM - Web Console

PFM - Agent for Service Response defines the Probe Daemon's task definitions and the IE Probe Daemon's task definitions in the measurement condition registration file (esptask.xml) in XML format. You can use PFM - Web Console to define these definitions in the measurement condition registration file.

This subsection describes how to use PFM - Web Console to add, delete, and edit the Probe Daemon's task definitions and the IE Probe Daemon's task definitions.

The following shows the procedure for adding, deleting, and editing the Probe Daemon's task definitions and the IE Probe Daemon's task definitions. For details about each procedure, see the indicated section.

[Figure]

You can distribute the defined tasks to the multiple Agent servers. For details about distributing, see 4.7.5 Distributing the Task information.

The task definition is loaded from the measurement condition registration file when the Probe Daemon and the IE Probe Daemon starts. If the definition is invalid, the Probe Daemon and the IE Probe Daemon stops and the measurements does not start. This case happens, for example, when PFM - Agent for Service Response does not find the Web transaction file defined in the task definition of the Web transaction. When you use PFM - Web Console to define the Web transaction task, PFM - Web Console checks whether the entered values are valid or not, but does not check whether the defined task is actually measurable. If the Probe Daemon and the IE Probe Daemon fails to start and stopped, check whether the measurement conditions are valid.

Note:

If you define the measurement condition registration file (esptask.xml) by editing the file directly and by using PFM - Web Console, note on the following. For details about editing the measurement condition registration file directly, see 8.3 Measurement condition registration file (esptask.xml).

If the measurement condition registration file has the XML syntax errors or the invalid task ID is given to the task definitions in the file, you cannot use PFM - Web Console to define the measurement conditions. Stop Agent Collector and the IE probe^#, edit the measurement condition registration file (esptask.xml), and start Agent Collector and the IE probe^#.

#: If you use the Windows services to start the IE probe service, it is not necessary to start the IE probe.

The maximum number of the tasks displayed in PFM - Web Console is 500. If 501 or more tasks are defined in the measurement condition registration file, the first 500 tasks are displayed and the others are not displayed in PFM - Web Console, and the message KAVF16023-W is output in the common message log.

If 501 or more tasks are defined and you delete a task in PFM - Web Console, 501th task is displayed in PFM - Web Console.
If the number of the tasks is more than 500 after adding the tasks, you cannot add a task in PFM - Web Console. If more than 500 tasks are displayed and you add a task in PFM - Web Console, the message KAVF16023-W is output in the common message log and you cannot add a task. In this case, the task is not registered in the measurement condition registration file, and is not created.
If you define a task in PFM - Web Console, the formatted comments and indents of the task is output to the measurement condition registration file.

Reference note:

PFM - Web Console sorts the tasks by the service type ID in ascending order and displays them. If the tasks have same service type ID, PFM - Web Console sorts the tasks by the measurement condition ID in ascending order. For details about the service type ID, see Common fields of 10. Records.

Organization of this section

To Page Top