List of definition files

Job Management Partner 1 Version 10, Job Management Partner 1/Performance Management - Agent Option for Service Response Description, User's Guide and Reference

7.1 List of definition files

The following table lists and describes the files that are used to set up an environment for PFM - Agent for Service Response and for registration of measurement conditions.

Table 7-1 Definition files used for environment setup

Definition file	File name	Description	See
Probe action condition definition file	installation-folder\agtv\probe\conf\esp.conf	Sets the IE Probe Daemon and the Probe Daemon's start options.	7.2
Measurement condition registration file	installation-folder\agtv\probe\task\esp\esptask.xml	Defines measurement conditions for each Internet service. The measurement conditions consist of a section for common conditions, and sections for service-specific conditions.	7.3
		Common section	7.3.2
		Service-specific condition sections	7.3.3
		for HTTP	7.3.3(1)
		for HTTPS	7.3.3(2)
		for SMTP	7.3.3(3)
		for POP3	7.3.3(4)
		for IMAP4	7.3.3(5)
		for DNS	7.3.3(6)
		for DHCP	7.3.3(7)
		for FTP	7.3.3(8)
		for TCP	7.3.3(9)
		for WEBTRANS	7.3.3(10)
		for IESCENA	7.3.3(11)
		for USERSERV	7.3.3(12)
IE scenario files	Any file name with the extension xml under installation-folder\agtv\probe\iescena\	Defines a series of operations as an IE scenario.	7.4
Web transaction files	Any file name with the extension xml under installation-folder\agtv\probe\webtrans\	Each defines a series of Web access operations as a single Web transaction.	7.5
Command registration file	installation-folder\agtv\probe\conf\espcommand.xml	Registers user-defined commands.	7.6
Measurement condition label definition file	installation-folder\agtv\probe\conf\esptasklabel.conf	Defines labels for measurement conditions.	7.7
IE Recorder action condition definition file	installation-folder\agtv\probe\conf\jpcvierec.conf	Defines the IE Recorder's action conditions.	7.8
Web Recorder action condition definition file	installation-folder\agtv\probe\conf\wr.conf	Defines the Web Recorder's action conditions.	7.9

Organization of this section: (1) About specification in XML format

(1) About specification in XML format

The measurement condition registration file, command registration file, and Web transaction files are created in XML format. The following points must be noted when you create definition files in XML format.

Start and end tags: XML tags must always be paired (start tag and end tag). If the end tag is missing for a specified start tag, or vice versa, an error results. Within a tag enclosed by angle brackets (< and >), you cannot specify any codes other than the tag name (such as spaces, tabs, or linefeed characters).

Element

The coding enclosed by a start tag and an end tag constitutes an element.

 
<SAMPLE_TAG>..element..</SAMPLE_TAG>

The start tag must have a corresponding end tag. In the example above, if <SAMPLE_TAG> were not accompanied by the corresponding </SAMPLE_TAG>, an error would result.

If there is no element, the start and end tags can be combined as follows:

 
<SAMPLE_TAG/>

Case: XML coding is case sensitive. You must enter all information exactly as shown in the definition file format.

Deletion of space, tab, and linefeed characters: Space, tab, and linefeed characters that were entered before or after an element are deleted; they are not treated as part of the element.

Characters requiring replacement

The characters listed below are reserved characters in the XML syntax. To use these characters as part of an element, they must be replaced with the indicated character strings.

Table 7-2 Characters requiring replacement

Character	Replacement character string
&	&
<	<
>	>
"	"
'	'

Specification of a comment

You can specify a comment in following format:

 
<!--comment-->

A comment text cannot contain two hyphens in succession (--).

Linefeed code: A linefeed code in a text is treated as LF(0x0a). To treat it as CRLF(0x0d0a), use 
 instead of the linefeed code.