Dynamic Virtual Elements

Suppose a protocol needs to be developed for a chassis that has a number of slots where cards of different types can be inserted. As it can be useful to have a DataMiner element for every card in the chassis, a protocol can be implemented in such a way that it can dynamically create an element for every card in the chassis: so-called Dynamic Virtual Elements (DVEs). This is only one use case illustrating the usefulness of DVEs. Many other use cases exist where DVEs can be useful.

A Dynamic Virtual Element (DVE) is an element that is dynamically created by a parent element. No data is stored for those elements; everything is managed by the parent element (hence the word virtual in DVE). The parent element is responsible for all communication with the DMS, and all parameters of the DVEs are derived from the parent element.

More information on DVEs is detailed in the following sections:

• Implementing DVE functionality
• Export rules
• Views
• Timeout state
• Severity state column
• Toggling DVE creation
• Remarks
• Exercise

Note

An example protocol "SLC SDF DVE" is available in the Protocol Development Guide Companion Files.

See also

DataMiner Protocol Markup Language:

• Protocol.Type:
  • options
  • overrideTimeoutDVE
• Protocol.ExportRules
• Protocol.Params.Param.ArrayOptions.ColumnOption@options:
  • element
  • severity

DataMiner Class Library:

• NT_DVE_CREATION_FLAG (340)

Best practices:

• DVE