Follow these guidelines when using dynamic models:

  • Create and verify dynamic models on a test Manager prior to deploying them into any production environment. The test Manager may be started and stopped several times during the process to verify the results of each step.

  • Create and edit the dynamic model files (those with extension .mdl) by using sm_edit.


    Only the .mdl files are created and edited by using sm_edit. The .ldm file generated by the dynmodel compiler must not be edited.

  • Classes that are related to each other should be contained in the same dynamic model file.

  • Dynamic model files can be loaded when a Manager is started or after the Domain Manager is already running. “Location and loading of dynamic model files” on page 24 provides additional information.

  • Perform a back up on the repository of the Manager before using dynamic modeling in a production environment.

  • 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 SDK.

  • 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 Service Assurance Manager.


    Changes made by using dynamic modeling may impact the performance and load of the Domain Manager.