Package Overview
The Ets_Model package provides an API for performing model operations like reading and writing model files. Riverbed Modeler uses various types of model files to manage the data associated with network representation and examination. Currently, only a subset of these files can be handled directly by the Ets_Model package; the only supported models are networks, projects, background traffic data, and public attribute descriptions.
In addition to examining the supported model files, the Ets_Model API can interact with the currently active Project Editor. There are functions to get the current project, the current network, the current selection set in the network, and whether or not the network has been saved since the last change. For network models, the Ets_Topo API provides a way to access all of the node, link, path, annotation, and subnet objects in the network. Changes made to objects in the current network will immediately be reflected in the Project Editor visual representation. For this reason, the Ets_Model API also provides a locking mechanism so that visual changes can be postponed until after a batch of attribute change are made.
A project can have multiple networks (one for each of the project’s scenarios) associated with it. The Ets_Pj (Project) API provides functions for accessing all of network models that belong to the project and not just the one in the current scenario.