Guidelines and requirements

A dynamic model file describes the model elements that extend the basic
VMware Smart Assurance
data model. The following guidelines apply to dynamic model files:
  • Typically, those classes that are related to each other are contained in the same dynamic model file.
  • Dynamic model filenames may contain ASCII letters (A..Z,a..z), ASCII numbers (0...9), and the underscore character (_), but may contain no other characters. The first character must be a letter.
  • The dynamic model filename must be unique within the first 23 characters.
  • The dynamic model file must have a .mdl filename extension.
  • Create and edit the dynamic model files (those with extension .mdl) by using
    sm_edit
    .
  • Dynamic model files must follow the syntax rules described in “Adding a class to the model” on page 78 and “Updating an existing class in the model” on page 80.
  • All refinements to a class
    must
    be contained in a single
  • refine interface
    <
    classname
    > declaration. For example, you cannot have a
  • refine interface Router
    declaration in the mymodel1.mdl file, and then another
    refine interface Router
    in the mymodel2.mdl. Likewise, you cannot have more than one
    refine interface Router
    declaration in the mymodel1.mdl file.
  • Precede any new attributes, classes, aggregates or events that are defined with a unique tag, such as “USR_”. You should not use "SM_" as this is already used by
    .
  • Avoid using the binary or byte data type, or the
    external
    keyword in any dynamic model files of the
    IP Manager
    that you will be copying over to the
    .
  • Dynamic model files must be located in either BASEDIR/smarts/model
    or
    BASEDIR/smarts/model/<
    config
    >. The
    <config>
    refers to the configuration directory that is specified on the command line when the
    Domain Manager
    is started.
  • The dynamic model files (those with extension .ldm) must be loaded into each
    that requires knowledge of the new topology and events. The loading of the dynamic model files incorporates them into the runtime data model.
  • When the option
    --
    dynamic is not added to the
    sm_server
    command, the
    will load
    all
    dynamic model files that can be loaded into a
    (those with extension .ldm) located in:
    BASEDIR/smarts/model/<
    config
    >
    The
    <config>
    refers to the configuration directory that is specified on the
    sm_server
    command line when the
    Domain Manager
    is started.
    Appendix B, The dynmodel Command Syntax and Options, provides information on creating dynamic model files that can be loaded into a
    .
  • When the
    --
    dynamic option is specified on the
    sm_server
    command line, the
    will load
    all
    dynamic model files that can be loaded into a
    (those with extension .ldm) located in:
    • BASEDIR/smarts/model
    • BASEDIR/smarts/model/<
      config
      >.
      The
      <config>
      refers to the configuration directory that is specified on the
      sm_server
      command line when the
      Domain Manager
      is started.
      Two dash (--) characters precede the dynamic option of
      sm_server
      .
      If a
      is started by using
      sm_service
      , edit the
      sm_service
      command to include the
      --
      dynamic option.