This appendix describes the default mappings between the Enterprise Manager alert data fields and the HP OpenView Operations message 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/HP_OVOU_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 HP OpenView Operations message format for the createEvent operation. |
|
updateEvent_request.xsl |
Transforms the Oracle Enterprise Manager alert data to the HP OpenView Operations message format for the updateEvent operation. |
|
getNewAlerts_response.xsl |
Transforms data in the HP OpenView Operations message 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 HP OpenView Operations message 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 there is a notification rule configured to invoke the OVOU connector. createEvent_request.xsl is invoked during the process to transform the data from Oracle Enterprise Manager format to OVOU message format. Table A–2 lists the default field mappings between the HP OpenView Operations message and the Oracle Enterprise Manager alert.
Table A-2 createEvent Operation Mappings
| OVO Event Attribute | OVO Attribute Type | Req'd? | Oracle Enterprise Manager Alert Attributes | Value |
|---|---|---|---|---|
|
Message Text |
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>* Key Values — <KeyValues>Message — <Message>Metric Column — <MetricColumn>Metric Name — <MetricName>* Notification Rule — <NotificationRuleName>Target Name — <TargetName>Target Type — <TargetType>Severity — <Severity>* URL — <EventPageURL> Fields preceded with an asterisk ( * ) are only present if the corresponding Enterprise Manager alert field has data. |
|
Severity |
String |
Yes |
Conditional based on the Oracle Enterprise Manager severity. |
Set to Normal if Oracle Enterprise Manager Severity is Information. Set to Critical if Oracle Enterprise Manager Severity is Critical. Set to Warning for all other Oracle Enterprise Manager Severity values. |
|
Message Group |
String |
Yes |
Value defaulted. |
OracleEnterpriseManager |
|
Object |
String |
Yes |
Set to the target name specified in the Oracle Enterprise Manager alert data. |
<TargetName> |
|
Node |
String |
Yes |
Value defaulted. |
OracleEnterpriseManager |
|
Application |
String |
Yes |
Set to the target name specified in the Oracle Enterprise Manager alert data. |
<TargetType> |
The Oracle Enterprise Manager Connector Framework invokes the updateEvent operation whenever an alert is generated in Oracle Enterprise Manager and there is a notification rule configured to invoke the OVOU connector. updateEvent_request.xsl is invoked during the process to transform the data from Oracle Enterprise Manager format to OVOU message format. Table A–3 lists the default field mappings between the HP OpenView Operations message and the Oracle Enterprise Manager alert.
Table A-3 updateEvent Operation Mappings
| OVO Event Attribute | OVO Attribute Type | Req'd? | Oracle Enterprise Manager Alert Attributes | Value |
|---|---|---|---|---|
|
Message text |
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>* Key Values — <KeyValues>Message — <Message>Metric Column — <MetricColumn>Metric Name — <MetricName>* Notification Rule — <NotificationRuleName>Target Name — <TargetName>Target Type — <TargetType>Severity — <Severity>* URL — <EventPageURL> Fields preceded with an asterisk ( * ) are only present if the corresponding Enterprise Manager alert field has data. |
|
Severity |
String |
Yes |
Conditional based on the Oracle Enterprise Manager severity. |
Set to Normal if Oracle Enterprise Manager Severity is Information. Set to Critical if Oracle Enterprise Manager Severity is Critical. Set to Warning for all other Oracle Enterprise Manager Severity values. |
|
Message Group |
String |
Yes |
Value defaulted. |
OracleEnterpriseManager |
|
Object |
String |
Yes |
Set to the target name specified in the Oracle Enterprise Manager alert data. |
<TargetName> |
|
Node |
String |
Yes |
Value defaulted. |
OracleEnterpriseManager |
|
Application |
String |
Yes |
Set to the target name specified in the Oracle Enterprise Manager alert data. |
<TargetType> |
The Oracle Enterprise Manager Connector Framework invokes the getNewAlerts operation on the poll cycle interval configured for the OVOU connector. One step in the operation is to send a request to the HP OpenView Operations web service for new alerts in HP OpenView Operations. When the response comes back, the getNewAlerts_response.xsl file is invoked to transform the HP OpenView Operations message data to the format required to create a new alert 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 HP OpenView Operations web service for updated alerts. When the response comes back, the getUpdatedAlerts_response.xsl file is invoked to transform the HP OpenView Operations message data to the format required to update the alert in Oracle Enterprise Manager.
Table A–4 lists the default field mappings between the HP OpenView Operations message 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 Event Attribute | OVO Attribute Type | Req'd? | Oracle Enterprise Manager Alert Attributes | Value |
|---|---|---|---|---|
|
key1 |
String |
Yes |
Set to the HP OpenView Operations message identifier. |
<Identifier> |
|
message |
String |
Yes |
Values from the alert context are listed in angle brackets in the Value column. |
Severity — <Severity>Message Group — <MessageGroup>Node — <Node>Object — <Object>Application — <Application>Service Name — <ServiceName>Message Key — <MessageKey> |
|
comment |
String |
Yes |
Set to message text. |
<MessageText> |
|
producerID |
String |
No |
Value defaulted. |
OVOU |
|
targetName |
String |
Yes |
Set to the node that reported the problem. |
<Node> |
|
TargetType |
String |
No |
Value defaulted. |
ovou_managed_node |
|
username |
String |
No |
Value defaulted to no value. |
|
|
password |
String |
No |
Value default to no value. |
|
|
metricName |
String |
Yes |
Set to the message group the alert belongs to. |
<MessageGroup> |
|
category |
String |
Yes |
Set to the message group. |
<MessageGroup> |
|
value |
String |
Yes |
Set to the transaction identifier. This is not part of the message data. It is provided by the web service for tracking transactions. |
<transactionID> |
|
severity |
String |
Yes |
Conditional based on the HP OpenView Operations severity and on the ResolvedBy field. |
Set to Clear if the ResolvedBy field is not empty. Set to Informational if the ResolvedBy field is empty and the HP OpenView Operations Severity is Normal. Set to Critical if the ResolvedBy field is empty and the HP OpenView Operations Severity is Major or Critical. Set to Warning if the ResolvedBy field is empty and any other HP OpenView Operations Severity value is specified. |