The Mappings page enables you to map columns of database tables to custom variables.
In the BSM Connector user interface, click in the toolbar. Then click Event >
Database.
In the BSM Connector user interface, click in the toolbar. Then click Metric >
Database.
Alternatively, double-click an existing policy to edit it.
Click Mappings to open the policy Mappings page.
A custom variable consists of a map name, an optional database table column, and one or more source and target value pairs. For example, you can assign the table column 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 and the source value is Serious
in the database record.
Table columns use the following syntax: <$DATA:<table_column>>
where <table_column>
is the name of the table column in the third-party database, for example <$DATA:severity>
.
For example, the custom variable mapSEVERITY
has the table column SEVERITY
assigned.
Assigning a table column to a map name is optional. If you do not assign a table column to a variable, you must add the source value directly to the variable when you insert the variable in an event attribute.
You can rearrange the information that appears in the lists by clicking the up or down arrows at the top of the list.
The Table Column tab shows the following information, if sample data is available:
Input Data Properties
If sample data is available, then the Input Data Properties section shows the table columns specified in the query.
Values for <table column>
The Values for <table column> section displays the values of a column selected in the Input Data 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 row, select the value and click
. The Database Sample Data window opens and shows all rows that have the selected value.
When you drag a column from the table columns list and drop it on the Default Value Mapping list, BSM Connector automatically adds the default prefix map
to the map name and inserts the table column. You can then drag one or more column source values from the values list and drop them on the Source Value list. You then finally only have to type the target values.
This task describes how to map table columns to custom variables.
Create one or more custom variables.
If you are working with sample data, drag the table column from the table column list to the Map Name column. BSM Connector automatically adds the default prefix map
to the map name and inserts the column name.
Alternatively, click above the Map Name column and type the variable name in the map name field. Columns are optional. If you do not assign a column to a variable, you must add the source value directly to the variable when you insert the variable in an event 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.
This section includes:
UI Element | Description |
---|---|
<Search Properties> ![]() ![]() |
Entered search string is used to find a table column. The list changes as you type; only matching items appear. To clear the search results, click |
![]() |
Find Matching Events. To find values that belong to more than one table row, select the value and click ![]() |
![]() |
Toggle Deduplication. Shows or hides duplicate values. |
Input Data Properties |
Shows all columns that are returned by the database query. Note: The Sample Data tab is empty if no sample data has been loaded into the policy or if the database query did not succeed. See also Configuring the Data Source in Database Policies. |
Values for <...> |
Displays the values of the column selected in the Input Data 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. |