Service Desk Practitioners Forum
cancel

OVOW - HPSD Import Mapping help needed

Highlighted
Saxo Javier
Respected Contributor.

OVOW - HPSD Import Mapping help needed

I hope someone can help me.

I have installed SD-OVO integration and I am having problems getting some information from the OVO events sent to HPSD incident.

I need to map the following information:

CI, Event ID and Source from OVO. I presume I need to use "Data Exchange - Import mapping" but I am not sure how to do this.

I have checked the SD documentation but I dont find it very clear, is there any papers that explain how to do this?

I dont know what information would be relevant to puclish here in order to get some help from you, so please ask anything and I will provide the info if you can.

Thank you very much in advance
7 REPLIES
Carol Hibbard
Acclaimed Contributor.

Re: OVOW - HPSD Import Mapping help needed

An import mapping with default values, called ovowindows, is provided
for the OpenView Operations integration, you can modify the import
mapping as needed.
Pradeep_30
Outstanding Contributor.

Re: OVOW - HPSD Import Mapping help needed

Hi,

OVOSD.vbs is the file which calls sd_event.exe with the parameters on windows. You can check for the parameters here. Specify the mapping in the external events and specify the parameters which you are passing from the sd_event.exe

HTH

Pradeep
Saxo Javier
Respected Contributor.

Re: OVOW - HPSD Import Mapping help needed

Thanks,

I think you answered my other thread as well :-)

The problem is the OVO attributes, there are some specific ones that I need to map to specific SD fields that we have in out organization, but I cannot find where those OVO attributes (like "Time First Created on Node" in an OVO event General tab) in order to define the mapping.

Does this explain my problem better?

TIA
Carol Hibbard
Acclaimed Contributor.

Re: OVOW - HPSD Import Mapping help needed

I'm not sure if I have the current version of the ovo-sd.vbs file but this should get you headed in the right direction. I'm also not sure I got the syntax right with the " characters.

At the beginning of the ovo-sd.vbs file, it captures the message attributes of interest. You would need to capture the additional attributes you want into a variable. Then later on in the script where it calls sd_event, you'd have to pass that variable to the SD field of preference, for example a custom field called msggrp. See inserts below about MsgGrp:

'======================================================================'
' Forwards Message to Service Desk, using Mode insert or update '
' VPW -> SD '
'======================================================================'

Function FwdMessage(Message, Mode)

' Get the message attributes we are interested in
MsgText = EscapeQuotes(Message.Text)
NodeId = Message.NodeName
OrigMsgText = EscapeQuotes(Message.OriginalText)
Application = EscapeQuotes(Message.Application)
Object = EscapeQuotes(Message.Object)
Severity = Message.Severity
MsgStatus = Message.State
MsgGrp = EscapeQuotes(Message.MessageGroup)

------------------------------
' Construct command to forward message to Service Desk
Command = """" & VPWBinToolsPath & "sd_event"" -m " & Mode & " -f """ &
VPWBinToolsPath & "sd_event.ini"" " &_
"-v event_id=" & MsgId & " description=""" & MsgText & """ impact=" & Severity
&_
" information=" & Information & " solution=""" & Instructions & """ ci=""" &
NodePrimaryName & """ status=" & MsgStatus & """ msggrp=" & MsgGrp


Sample message below to show the OVOW message field names.


1: C:\>GenericEventAsyncConsumer.wsf "Select * From __InstanceCreationEvent
Where TargetInstance ISA 'OV_Message'"
/Namespace:root\HewlettPackard\OpenView\Data
2: Microsoft (R) Windows Script Host Version 5.6
3: Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.
4:
5: Waiting for events...
6:
7: BEGIN - OnObjectReady.
8: Thursday, 20 June, 2002 at 16:36:49: '__InstanceCreationEvent' has been triggered.
9: TargetInstance (wbemCimtypeObject)
10: AcknowledgeAfterTroubleTicket = False
11: AgentId = 059bbdd0-7eed-71d6-1e0e-0a0a0a060000
12: Application = OS
13: AutomaticAction = (null)
14: ConditionId = 000000000000000000000000000000000000
15: CreateTroubleTicketInterface = False
16: DoNotification = False
17: *Id = 275d13b0-845b-71d6-161d-0a0a0a060000
18: InstructionAvailable = False
19: IsProxied = False
20: LogOnly = False
21: MessageGroup = WINOSSPI-CORE
22: MessageKey = net-dpen6450.LissWare.NET WINOSSPI-SysMon_CacheFaultsSec
23: MessageKeyRelation = net-dpen6450.LissWare.NET WINOSSPI-SysMon_CacheFaultsSec
24: NodeName = {A0151862-79D6-47F9-8952-97F563F29429}
25: NumberOfAnnotations = 0
26: Object = Cache
27: OperatorAction = (null)
28: OriginalId = 000000000000000000000000000000000000
29: OriginalServiceId = WINOSSPI:NT:Memory:Cache@@<$MSG_NODE_ID>
30: OriginalText = Monitor WINOSSPI-SysMon_CacheFaultsSec: Threshold:... Value: 77.17
31: ServiceId = WINOSSPI:NT:Memory:Cache@@{A0151862-79D6-47F9-8952-97F563F29429}
32: Severity = 4
33: Source = WINOSSPI-SysMon_CacheFaultsSec(7.0)
34: SourceType = 8
35: State = 2
36: Text = Object: Memory, Counter: Cache Faults/sec: The threshold of 15 ...
37: TimeCreated = 20-06-2002 16:36:49 (20020620163649.000000+120)
38: TimeOfStateChange = 20-06-2002 16:36:49 (20020620163649.000000+120)
39: TimeReceived = 20-06-2002 16:36:49 (20020620163649.000000+120)
40: Type (wbemCimtypeString) =
41: Unmatched (wbemCimtypeBoolean) = False
42: UsedNotificationInterfaces (wbemCimtypeString) =
43: UserOfStateChange (wbemCimtypeString) =
44: END - OnObjectReady.
..:
50: Finished.
Pradeep_30
Outstanding Contributor.

Re: OVOW - HPSD Import Mapping help needed

There are ssome scripts on ovinternals.com regarding getting the message properties. Try this pass them as parameters to sd_event.exe and map those parametersto appropriate fields in external mapping.

HTH
Saxo Javier
Respected Contributor.

Re: OVOW - HPSD Import Mapping help needed

Thanks, this is showing me the light now :-)

I still miss some stuff (basically because I have no experience whatsoever with this)...

The way I understand this, this part in ovo-sd.vbs:

'======================================================================'
' Forwards Message to Service Desk, using Mode insert or update '
' VPW -> SD '
'======================================================================'

Function FwdMessage(Message, Mode)

' Get the message attributes we are interested in
MsgText = EscapeQuotes(Message.Text)
NodeId = Message.NodeName
OrigMsgText = EscapeQuotes(Message.OriginalText)
Application = EscapeQuotes(Message.Application)
Object = EscapeQuotes(Message.Object)
Severity = Message.Severity
MsgStatus = Message.State
MsgGrp = EscapeQuotes(Message.MessageGroup)

Defines what attributes are being looked at in the OVO message.

And this part in ovo-sd.vbs:
' Construct command to forward message to Service Desk
Command = """" & VPWBinToolsPath & "sd_event"" -m " & Mode & " -f """ &
VPWBinToolsPath & "sd_event.ini"" " &_
"-v event_id=" & MsgId & " description=""" & MsgText & """ impact=" & Severity
&_
" information=" & Information & " solution=""" & Instructions & """ ci=""" &
NodePrimaryName & """ status=" & MsgStatus & """ msggrp=" & MsgGrp

Defines how those attributes are mapped or "sent" to SD. Correct?

with the MsgGrp example, I understand that there is a field in SD called "MsgGrp" and that the information in that field comes from the entry
"MsgGrp = EscapeQuotes(Message.MessageGroup)"

The problem is that I still dont understand how this works.

Example, I need to prefill "Actual Start" in Service Desk with the TimeCreated attribute from OVO. The "EscapeQuotes..." is something I dont understand either.

Thanks
Carol Hibbard
Acclaimed Contributor.

Re: OVOW - HPSD Import Mapping help needed

Yes, you are understanding the process and the example provided showing how to get the MsgGrp added for use in the import mapping. Now you need to do the same thing for your fields of interest. So for the case of created time, it appears that this is in the TimeCreated field. You should use the EscapeQuotes when reading any text field. Severity and status are numeric fields in OVOW that have to mapped to the desired code fields in SD. You will likely need to do some massaging of this time field to use it successfully in your SD Actual Start field.