beautypg.com

Classes, Hpsvsp_cim_listenerdestinationcimxml, Class introduction – HP SAN Virtualization Services Platform User Manual

Page 274

background image

Classes

HPSVSP_CIM_ListenerDestinationCIMXML

Class introduction

Instances of ListenerDestinationCIMXML represent portals to clients interested in receiving indications
from a SMI agent. Clients are responsible for creating an instance of ListenerDestinationCIMXML using
the intrinsic instance function createInstance(), and removing it when no longer interested in listening
for indications using intrinsic instance function deleteInstance().

According to the rules of Indication Profile v1.4:

1.

If a client creates a ListenerDestinationCIMXML instance in a vendor namespace, then a duplicate
ListenerDestinationCIMXML instance (with all of the same properties) is created in the SMI agent's
Interop namespace.

2.

If a client creates a ListenerDestinationCIMXML instance in the SMI agent's Interop namespace,
no duplicate instances are created elsewhere.

3.

If a client deletes a ListenerDestinationCIMXML instance, the instance is removed from the SMI
agent Interop namespace, and the vendor namespace, if present.

Depending on the CIMOM chosen for the implementation, a provider capable of creating instances
may already be present in the CIMOM.

This has the following ramifications:

1.

The developer may not need to implement a provider for ListenerDestinationCIMXML (consult the
documentation for the chosen CIMOM).

2.

The provider developer may need to remove the existing CIMOM's provider, and create their
own to follow the rules of the Indication Profile v1.4.

3.

If the CIMOM implementation does not support option 2, then the Indication Profile advertised
by the Profile Registration Profile may need to drop to Indication Profile version 1.3 or 1.2.

ListenerDestinationCIMXML

instances are uniquely identified by 4 keys: Name,

SystemCreationClassName

, SystemName, CreationClassName. The provider developer

ignores any key value passed in the createInstance() call, and assigns the key properties values that
are appropriate for the CIMOM. Clients are expected to use the object path returned from the
createInstance() call (if successful) as a handle to the ListenerDestinationCIMXML instance.

Indication Profile

274