Hitachi

JP1 Version 11 JP1/Performance Management - Agent Option for Service Response Description, User's Guide and Reference


8.1.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 8‒2: Characters requiring replacement

Character

Replacement character string

&

&amp;

<

&lt;

>

&gt;

"

&quot;

'

&apos;

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 &#xD;&#xA; instead of the linefeed code.