Forwarding message changes

HPOM for Windows allows you to modify a message in various ways:

• Add and modify annotations
• Change severity and message text
• Own, disown, acknowledge, and unacknowledge messages

All these modifications can be forwarded to the trouble-ticket system that has received the original copy of the message. On the HPOM for Windows side this is fairly simple; the HP Operations server generates change events which can be caught by another WMI policy. Then, these change events must be associated with the created trouble ticket which must meet the following requirements:

• The trouble-ticket must contain the HP Operations Message ID as attribute
• There must be an external mapping mechanism which finds the TT ID for an HP Operations Message ID

Because this has to be done in the interface script/program attached to the WMI export policy (outside of HPOM for Windows) and also depends on the trouble-ticket software itself, it will not be discussed here.

See Example policies and scripts for message forwarding for an example of such a message modification policy (UpdateTT policy) and the example script, UpdateTT.vbs.

The UpdateTT policy takes advantage of WMI events generated by the HP Operations server whenever a message is modified. To register for change events, use either the generic class OV_Message_ChangeEvent (to register for any change events) or the derived event classes (which represent specific change events):

• OV_Message_SeverityChangeEvent
• OV_Message_TextChangeEvent
• OV_Message_NumberOfAnnotationsChangeEvent
• OV_Message_StateChangeEvent
• OV_MessageAction_StateChangeEvent

Either the generic or derived classes can be used to listen for message modifications. You must create a separate WMI policy for each change event class, because WMI policies cannot be bound to multiple objects or events in parallel.

As in the initial submission policy, there must be a script called as an automatic command. The script must verify itself whether the change event applies to a message which has been submitted to a trouble-ticket system in the first place. There is no way to specify policy rules filtering for certain message attributes (like the TT-Flag or application, object, ...).

Related Topics:

• Example policies and scripts for message forwarding