This appendix describes the default mappings between the Enterprise Manager alert data fields and the Microsoft SCOM alert data fields. The data is formatted in XML, and the XSLT files transform the data from one format to another.
For information on customizing the field mappings, see Section 4.1, "Customizing Mappings".
This appendix discusses the following topics:
Data Translation Files
createEvent Operation
updateEvent Operation
getNewAlerts and getUpdatedAlerts Operations
XML Style Sheet (XSL) files contain the mappings between the two systems. These files are located in the following directory:
$ORACLE_HOME/sysman/connector/SCOM_Connector
Table A–1 lists the XSL files that perform the mappings and provides a summary of each.
Table A-1 XSL Files that Perform Mappings
| File | Description |
|---|---|
|
createEvent_request.xsl |
Transforms the Oracle Enterprise Manager alert data to the Microsoft SCOM alert format for the createEvent operation. |
|
updateEvent_request.xsl |
Transforms the Oracle Enterprise Manager alert data to the Microsoft SCOM alert format for the updateEvent operation. |
|
getNewAlerts_response.xsl |
Transforms data in the Microsoft SCOM alert format to the Oracle Enterprise Manager alert format. This file is invoked to transform the response for the getNewAlerts poll operation. |
|
getUpdatedAlerts_response.xsl |
Transforms data in the Microsoft SCOM alert format to the Oracle Enterprise Manager alert format. This file is invoked to transform the response for the getUpdatedAlerts poll operation. |
The following sections provide details about the default mappings in each of the files.
The Oracle Enterprise Manager Connector Framework invokes the createEvent operation whenever an alert is generated in Oracle Enterprise Manager and a notification rule is configured to invoke the SCOM connector. createEvent_request.xsl is invoked during the process to transform the data from Oracle Enterprise Manager format to SCOM alert format. Table A–2 lists the default field mappings between the Microsoft SCOM alert and the Oracle Enterprise Manager alert.
Table A-2 createalert Operation Mappings
| SCOM Field | SCOM Attribute Type | Req'd? | Oracle Enterprise Manager Alert Attributes | Value |
|---|---|---|---|---|
|
Name |
String |
Yes |
Set to the Metric Column. |
<MetricColumn> |
|
Description |
String |
Yes |
Values from the alert context are listed in angle brackets in the Value column. |
Received alert reported by Oracle Enterprise Manager: Collection Time — <Collection Time>Target Type — <TargetType>Target Name — <TargetName>Metric Name — <MetricName>Metric Column — <MetricColumn>* Key Values — <KeyValues>Severity — <Severity>* Notification Rule — <NotificationRuleName>* URL — <EventPageURL>Message — <Message> Fields preceded with an asterisk ( * ) are only present if the corresponding Enterprise Manager alert field has data. |
|
Priority |
String |
Yes |
Conditional based on the Oracle Enterprise Manager severity. |
Set to Low if Oracle Enterprise Manager Severity is Information. Set to Normal if Oracle Enterprise Manager Severity is Critical. Set to High for all other Oracle Enterprise Manager severity values. |
|
Severity |
String |
Yes |
Conditional based on the Oracle Enterprise Manager severity. |
Set to Information if Oracle Enterprise Manager Severity is Information. Set to Error if Oracle Enterprise Manager Severity is Critical. Set to Warning for all other Oracle Enterprise Manager severity values. |
The Oracle Enterprise Manager Connector Framework invokes the updateEvent operation whenever an alert is generated in Oracle Enterprise Manager and a notification rule is configured to invoke the SCOM connector. updateEvent_request.xsl is invoked during the process to transform the data from Oracle Enterprise Manager format to SCOM alert format. Table A–3 lists the default field mappings between the Microsoft SCOM alert and the Oracle Enterprise Manager alert.
Table A-3 updateEvent Operation Mappings
| SCOM Field | SCOM Attribute Type | Req'd? | Oracle Enterprise Manager Alert Attributes | Value |
|---|---|---|---|---|
|
Id |
String |
Yes |
Set to the External Event Id. |
<ExternalEventId> |
|
Resolution State |
String |
Yes |
Conditional based on the Oracle Enterprise Manager severity |
Set to 255 (Closed) if Oracle Enterprise Manager Severity is Clear, Unreachable End, Blackout End, Metric Error End, or End. Set to 0 (New) for all other Oracle Enterprise Manager severity values. |
|
Alert History |
String |
No |
Conditional based on the Oracle Enterprise Manager severity. |
Set to " Oracle Enterprise Manager cleared alert" if Oracle Enterprise Manager severity is Clear. Set to " Oracle Enterprise Manager changed alert severity to warning" if Oracle Enterprise Manager severity is Warning. Set to " Oracle Enterprise Manager changed alert severity to critical" if Oracle Enterprise Manager severity is Critical. Not set for other Oracle Enterprise Manager severity values. |
The Oracle Enterprise Manager Connector Framework invokes the getNewAlerts operation on the poll cycle interval configured for the SCOM connector. One step in the operation is to send a request to the Microsoft SCOM web service for new alerts in Microsoft SCOM. When the response comes back, the getNewAlerts_response.xsl file is invoked to transform the Microsoft SCOM alert data to the format required to create new alerts in Oracle Enterprise Manager.
After the getNewAlerts operation is complete, the Enterprise Manager Connector Framework performs the getUpdatedAlerts operation. Like the getNewAlerts operation, it sends a request to the Microsoft SCOM web service for updated alerts. When the response comes back, the getUpdatedAlerts_response.xsl file is invoked to transform the Microsoft SCOM alert data to the format required to update the alerts in Oracle Enterprise Manager.
Table A–4 lists the default field mappings between the Microsoft SCOM alert and the Oracle Enterprise Manager alert. These mappings are applicable to new and updated alerts, and must always be the same.
Table A-4 getNewAlerts and getUpdatedAlerts Operation Mappings
| Oracle Enterprise Manager alert Attribute | Attribute Type | Req'd? | SCOM Alert Attributes | Value |
|---|---|---|---|---|
|
key1 |
String |
Yes |
Set to the Microsoft SCOM alert identifier. |
<Identifier> |
|
message |
String |
Yes |
Values from the alert are listed in angle brackets in the Value column. |
Name — <Name>Computer Name — <NetbiosComputerName>Severity — <source>Object — <Severity>Rule Id — <MonitoringRuleId> |
|
comment |
String |
Yes |
Values from the alert are listed in angle brackets in the Value column. |
Resolution State — <Status>Message — <Description> |
|
producerID |
String |
No |
Value defaulted. |
SCOM |
|
targetName |
String |
Yes |
Conditional based on the Microsoft SCOM Principal Name. |
Set to <PrincipalName> if the SCOM Principal Name contains data. Set to Unknown if the SCOM Principal Name is blank or missing. |
|
TargetType |
String |
No |
Value defaulted. |
scom_managed_host |
|
username |
String |
No |
Value defaulted to no value. |
|
|
password |
String |
No |
Value default to no value. |
|
|
metricName |
String |
Yes |
Set to the SCOM alert source. |
<Source> |
|
category |
String |
Yes |
Set to the SCOM alert source. |
<Source> |
|
value |
String |
Yes |
Set to the transaction identifier. This is not part of the alert data. It is provided by the web service for tracking transactions. |
<transactionID> |
|
severity |
String |
Yes |
Conditional based on the Microsoft SCOM status and severity. |
Set to Clear if the SCOM status is set to 255 (Closed). Set to Informational if the SCOM status is not set to 255 and the SCOM severity is Information. Set to Critical if the SCOM status is not set to 255 and the Microsoft SCOM severity is Error. Set to Warning if the SCOM status is not set to 255 and any other SCOM severity value is specified. |