Simplified Model

As Common Data Model causes problems, a new Simplified Model for storing data is introduced in TADDM 7.3 version. The only elements that are left from the old model are classes.

With the new Simplified Model, you can create script-based, custom sensors more easily and extend the scope of discovery. You can customize new sensors and edit the existing ones.

Note: Simplified Model is not supported for other products that you integrate with TADDM.
The following table lists the most important features introduced with Simplified Model and provides the location where you can find more information about them.
Table 1. Simplified Model features
Feature Location
Top-level generic classes in the hierarchy that represent crucial CIs. Package, classes, and hierarchies
New middle-level objects that represent deployable components. Package, classes, and hierarchies
A mechanism to extend new top levels with the unlimited number of attributes (extended attributes). Extended attributes
A mechanism to store entire chunks of raw data (for example XMLs, or command outputs) and attach them to the top-level CIs (extended instances). Extended instances
New eval operator used in MQL queries for extended attributes and extended instances. Model Query Language overview
New generic naming rule attribute openId. OpenId generic naming rule attribute

Package, classes, and hierarchies

Package and classes
All new classes are stored in the com.collation.platform.model.topology.simple package. The classes names start with the capital letter "S" to avoid conflicts because TADDM differentiates data types by their short names.
Hierarchy attributes
Each data model object contains two hierarchy attributes, hierarchyDomain and hierarchyType, which define information that in the old model was present in the package and type of every class. For example, the ComputerSystem type contained many specific computer systems that represented different operating systems like sys.linux.LinuxUnitaryComputerSystem or sys.windows.WindowsComputerSystem. These objects had to be stored separately. The new simplified model allows for storing objects of both types as the SComputerSystem type, when these two attributes are set in the following way:
  • For sys.linux.LinuxUnitaryComputerSystem:
    hierarchyDomain="sys.unix.linux"
hierarchyType="RedHat"
  • For sys.windows.WindowsComputerSystem:
    hierarchyDomain="sys.windows"
hierarchyType="Windows7"
The hierarchyDomain attribute values specify levels of domain, beginning with the most general level and finishing with the most specific one. For example, in the "app.db.mongodb" value, app is an application server, db is a database server, and mongodb is a specific database, in this case MongoDB.
The hierarchy attributes are used to fully handle UI. They are also used in querying.
New hierarchy types
The following list shows new hierarchy types:
  • SComputerSystem - replaces the ComputerSystem hierarchy.
  • SSoftwareServer - replaces the AppServer hierarchy.
  • SLogicalGroup - replaces the AppServerCluster hierarchy and represents any kind of collections that are stored by a sensor, for example, clusters, or domains.
  • SFunction - replaces the Function hierarchy and represents additional rules and functions.
  • SSoftwareInstallation - represents a physical software packages that are present on a computer system that constitutes a software server (vendor created libraries).
  • SPysicalFile - replaces AppConfig and LogicalContent hierarchies and represents a configuration file. The whole content of this file is captured by a discovery.
  • SDeployableComponent - a new type that represents types that are considered as relationship sources or targets, which are deployed on computer systems, software servers, or logical groups. They are middle-level objects. Some of the old CDM types are still attached to SDeployableComponent hierarchy to ensure compatibility with earlier versions. The following list specifies such types:
    • BiztalkApplication
    • Database
    • DominoDatabase
    • ExchangeLink, ExchangeStorageGroup
    • FileSystem
    • IIsWebServer, IIsWebVirtualDir
    • MBExecutionGroup, MBMessageFlow, MessageBox
    • MQChannel, MQQueue
    • OracleSchema
    • SharePointWebApplication
    • SoftwareModule - the only component of the SoftwareModule type that is left is J2EEApplication as it is the only deployable component in this type.
    • WebVirtualHost
All these new types inherit from the following abstract types that are introduced into data model for modeling purposes: SStandaloneObject, SContextualObject, SGroup.
lastStoreTime attribute
The lastModifiedTime attribute is deprecated because it has a misleading name. A new lastStoreTime attribute replaces it.

Migration

The migration from the old model to the new one is automatic. You do not need to complete any additional tasks. The MQL queries and SQL views are compatible with earlier version.

Changes in Data Management Portal

In the Inventory Summary pane on the Inventory tab, there is a new component type called Generics. You can find there objects of classes from the simple package. You can also browse generic folders in the Discovered Components pane and display details for discovered objects of new class types. For information about displaying extended attributes and extended instances, see Extended attributes and Extended instances.

Business applications

The Simplified Model is supported by business application engine. You can use new classes, attributes, and the eval operator in queries while working with business applications. You can also create business application from the objects that you store by using the new model.