The source page of the XML file policy editor enables you to specify which XML file the policy reads. You can also set options that configure how the policy reads the file.
In the BSM Connector user interface, click in the toolbar. Then click Event >
XML File.
In the BSM Connector user interface, click in the toolbar. Then click Metric >
XML File.
In the BSM Connector user interface, click in the toolbar. Then click Topology >
XML File.
In the BSM Connector user interface, click in the toolbar. Then click Generic output >
XML File.
Alternatively, double-click an existing policy to edit it.
Click Source to open the policy Source page.
XML files must meet the following criteria so that they can be processed correctly by XML file policies:
XML file requirements:
Use file rolling to create two or more XML input files.
You can use the asterisk (<*>) wildcard string in the Log File Path / Name text box on the Source page to match multiple file names. For example, to match the XML source file names events.1.xml
and events.2.xml
, use the pattern <path>/events<*>.xml
in the Log File Path / Name text box. Note that the <*> wildcard string is the only supported OMi pattern in log file paths. For more information on pattern matching, see Pattern-Matching Details.
When using file rolling, make sure the Close after reading option on the Source page is selected.
Make sure the polling interval is shorter than the frequency in which data is written to the file. The polling internval must not be shorter than 15 s
, otherwise the policy cannot be saved.
XML format requirements:
The root element is optional.
If a root element exists, it must not be closed by its end tag.
All other XML elements must be complete.
The following example XML document begins with the root tag <AllAlerts>
and contains two types of events: performance alerts and availability alerts. If you define the XML elements <PerformanceAlert>
and <AvailabilityAlert>
as XML event tags in the Source page of XML file policies, only those events are processed by XML file policies.
Example:
<AllAlerts>
<AvailabilityAlert>
<Title>Host Unreachable</Title>
<Severity>Critical</Severity>
<TimeOccured>02/11/10 03:52:18AM</TimeOccured>
<Object>Host:fish.example.com</Object>
</AvailabilityAlert>
<PerformanceAlert>
<Title>Disk IO rate high</Title>
<Severity>Warning</Severity>
<TimeOccured>02/11/10 04:08:31AM</TimeOccured>
<Object>Disk:disk0:dog.example.com</Object>
</PerformanceAlert>
<AvailabilityAlert>
<Title>Web Application unresponsive</Title>
<Severity>Critical</Severity>
<TimeOccured>02/11/10 05:01:26AM</TimeOccured>
<Object>WebApp:http://employeeportal.intra.example.com</Object>
</AvailabilityAlert>
<PerformanceAlert>
<Title>Phyiscal Read Rate high for Bufferpool BP1</Title>
<Severity>Warning</Severity>
<TimeOccured>02/11/10 08:37:09AM</TimeOccured>
<Object>DB:USRDB:cat.example.com</Object>
</PerformanceAlert>
<PerformanceAlert>
<Title>Phyiscal Read Rate high for Bufferpool BP1</Title>
<Severity>Warning</Severity>
<TimeOccured>02/11/10 08:37:09AM</TimeOccured>
<Object>DB:USRDB:cat.example.com</Object>
</PerformanceAlert>
</AllAlerts>
XML files must follow the topology discovery syntax. See Topology Discovery Syntax.
This task describes how configure the XML source file and how the policy reads it.
Type the full path to the XML file on the BSM Connector system.
Click to load a sample XML file. You can load a sample file from the BSM Connector system or from the system where the Web browser runs.
When you load sample data, BSM Connector replaces already loaded data with the new data. This does not affect any mappings that are defined based on previously available sample data.
Click to create one or more XML tags. You can create a tag manually by typing the XML element. If you are working with sample data, you can create a tag by double-clicking the XML element in the list.
The XML tag creates a shortcut to the XML element that you want the policy to process. An event tag typically identifies an event record in an XML log file, while a metric tag identifies a metric record in an XML log file. You can define more than one XML tag. For example, an XML file may contain two types of events: <PerformanceAlert>
and <AvailabilityAlert>
. To process both types, define both elements as event tags.
This task describes how configure the XML source file and how the policy reads it.
Type the full path to the XML file on the BSM Connector system.
Enter the age to deletion - the number of times for the policy to be run for a host that is not part of the topology data. After this number of policy executions, this host is deleted from the server.
Optionally, enable delta detection, so that only the difference between the received XML file and the repository is sent to the topology server.
UI Element | Description | ||||||
---|---|---|---|---|---|---|---|
Log File Path / Name
Topology XML File
|
Path and name of the You can use the following configurations to make your policy more flexible:
Note:
|
||||||
Polling Interval |
Determines how often the policy reads the Note that a policy begins to evaluate data after the first polling interval passes, unless the Default value: 5 minutes Note: Make sure that you set this value to a minimum of |
||||||
Logfile Character Set
|
Name of the character set used by the Note: It is important to choose the correct character set. If the character set that the policy is expecting does not match the character set in the Default value: UTF-8 |
||||||
Send event if log file does not exist
Send OMi event if topology file does not exist
|
Default value: not selected |
||||||
Close after reading |
If you select this option, the file handle of the If you do not select this option, the file handle remains and is read entirely each time, unless there is a newer file with the same name (or name pattern). In that case the original Consider the following example: a policy reads the In case this option is selected, the unread data from the In case this option is not selected, the unread data from the new Default value: not selected |
||||||
Read Mode
|
The read mode of
Note: Every policy reads the same Default value: Read from last position |
||||||
Sample Data
|
Enables you to upload an XML sample file. |
||||||
![]() |
Load sample data from server. Loads an XML sample file from the OMi Load sample data from local file system. Loads an XML sample file from the system where the Web browser runs. Note: BSM Connector can only load a maximum of 50 MB of sample data. |
||||||
![]() |
Opens the XML Sample Data dialog box. This dialog box displays the contents of the uploaded XML sample file. | ||||||
XML Event Tag
(Events only) |
Enables you to specify one or more XML event tags. The XML event tag creates a shortcut to the XML element that you want to process. An event tag typically identifies an event record in an XML file. You can define more than one event tag. |
||||||
![]() |
Create new XML event tag manually. Enables you to type an XML element in the provided box. Create new XML event tag from XML sample data. Opens the XML Sample Data Outline dialog box. This dialog box displays the XML elements and attributes contained in the uploaded XML sample data. |
||||||
![]() |
Deletes the selected XML event tag. Caution: Deleting an event tag that is referenced in a policy corrupts the policy and renders it unusable. |
||||||
XML Metric Tag
(Metrics only) |
Enables you to specify one or more XML metric tags. The XML metric tag creates a shortcut to the XML element that you want to process. A metric tag typically identifies a metric record in an XML file. You can define more than one metric tag. |
||||||
![]() |
Create new XML metric tag manually. Enables you to type an XML element in the provided box. Create new XML metric tag from XML sample data. Opens the XML Sample Data Outline dialog box. This dialog box displays the XML elements and attributes contained in the uploaded XML sample data. |
||||||
![]() |
Deletes the selected XML metric tag. Caution: Deleting a metric tag that is referenced in a policy corrupts the policy and renders it unusable. |
||||||
Detect deltas
(Topology only) |
A delta is the difference between the received XML file and the repository. The delta is the bare minimum of information about the changes. It discovers all changes without regards to the RTSM model. If an instance or relation is not discovered for a certain amount of time (Age to deletion), it is deleted. The counter goes up each time when the algorithm is running (this depends on the interval and the last time the file was written / sent via web service). If not selected,no delta detection is done and the incoming topology file is directly sent to the topology server. Default value: selected. |
||||||
Age to deletion(Topology only) |
A number of times for the policy to be run for a host that is not part of the topology data. After this number of policy executions, this host is deleted from the server. |