The Mappings page enables you to map key and value strings contained in Web service requests to custom variables.
In the BSM Connector user interface, click in the toolbar. Then click Event >
REST Web Service Listener.
In the BSM Connector user interface, click in the toolbar. Then click Metrics >
REST Web Service Listener.
Alternatively, double-click an existing policy to edit it.
Click Mappings to open the policy Mappings page.
A custom mapping definition consists of a map name (variable), an optional input data property (XML element or XML attribute), and one or more source and target value pairs. For example, you can assign the XML element Severity
to the map name mapSeverity
, and add a source value of serious
. You can then assign the target value critical
to the variable so that BSM Connector inserts the value critical
into the event in all places where the variable is used.
XML properties use the following syntax: <$DATA:/<XMLProperty>
>
<XMLProperty>
is the path from the root XML element of XML data to a specific XML element or attribute within that data. XML path uses slashes (/) as the path delimiters.
For example, the custom definition with the mapSeverity
map name has the input data property of <$DATA:/PerformanceAlert/Severity>
where Severity
is a child element of PerformanceAlert
.
XML properties are optional. If you do not assign an input data property to a map name (variable), you must add the source value directly to the variable when you insert the variable in an event attribute.
Note: The Sample Data tab is empty if no sample data has been loaded into the policy or if the sample data does not match any specified XML tags.
The Sample Data tab shows the following information if sample data is available:
XML Properties
If sample data is available, the XML Properties section of the Sample Data tab shows all XML elements and attributes that match an XML tag.
The XML Properties section by default shows the short path to the XML property or value. To view the full path, click . The full path begins with the XML tag specified in the Source tab.
The items in the XML Properties section are by default sorted alphabetically in ascending order.
To search for an XML property or value, type the search string in the Search Properties box. The list changes as you type; only matching items appear.
Values for <XMLProperty>
This section displays the values of an XML property selected in the XML Properties section. If a value appears more than once, click to show or hide duplicate values. To find values that belong to more than one XML property, select the value and click
. The XML Sample Data window opens and shows all XML properties that have the selected value.
This task describes how to map XML elements and attributes to custom variables.
Create one or more custom variables.
If you are working with sample data, drag the XML elements or attributes from the XML Properties list to the Map Name column. BSM Connector automatically adds the default prefix map
to the map name and inserts the correct path to the XML property.
Alternatively, click above the Map Name column and type the variable name in the map name field. XML properties are optional. If you do not assign an XML property to a variable, you must add the source value directly to the variable when you insert the variable in an event or a metric attribute.
Add source and target value pairs to each custom variable.
If sample data is loaded in
above the Source Value column and type the source and target values in the corresponding fields.
Optional. In the Indicators tab, add indicators to the source or target value fields. After loading the indicators from the OMi server, the Indicators tab shows a hierarchy of configuration item types.
To insert an indicator in a source or target value field, drag the indicator state (for example, HTTPServer:Normal
) from the Indicators tab and drop it on the corresponding field.
Optional. In the Policy Variables tab, add policy variables to
HP recommends to surround variables with quotation marks, for example "<$MSG_NODE>"
or "<$MSG_GEN_NODE>"
, at least for those variables whose values can contain space characters.
UI Element | Description |
---|---|
<Search Properties> ![]() ![]() |
Entered search string is used to find an XML property. The list changes as you type; only matching items appear. To clear the search results, click |
![]() |
Toggle Short/Full Path Notation. Shows or hides the full path to the XML property. The full path starts with <xml event/metric tag> /<path to xml property> . The XML properties section by default shows the short path to the XML property. |
![]() |
Find Matching Events. To find values that belong to more than one XML property, select the value and click |
![]() |
Toggle Deduplication. Shows or hides duplicate values. |
XML Properties |
Shows all XML properties that have been received by the REST Web service listener for this policy. Note: The Sample Data tab is empty if no sample data has been loaded into the policy or if no XML data has been received for the policy. For information about loading sample data into a REST Web service listener policy, see Events and Metrics only: How to load sample data into the policy. |
Values for <...> |
Displays the values of the XML properties selected in the XML Properties section. |
Description |
|
---|---|
![]() |
Refresh. Loads the configured indicators from the Note:
|
<Search …> |
Entered search string is used to search the indicators and highlight only the indicators containing the specified string. To search for indicators with specific text strings in the name, type the string in the <Search …> field and click the |
<Indicators> |
Hierarchy of configuration item types with associated health indicators (HIs), which are applicable for the event integration only, and event type indicators (ETIs). To insert an indicator with a state in a policy, drag and drop the indicator from the Indicators tab to the relevant field in the policy. |