Data views in the TADDM model

You can generate reports from the TADDM data model file, model.xml file.

The data model is organized into several namespaces. The namespace is a logical container in which all the names are unique. Each namespace contains query subjects, query items, and objects. The following namespaces are present after you import the TADDM model.xml file:

CDM namespaces

These views contain the query subjects for almost all Common Data Model classes, including discovery-related classes, split into several namespaces by their package names. Package names are sorted alphabetically. The Simplified Model classes are distinguished by the simple prefix in the namespace name. You can use this data to generate reports that contain different types of CDM objects.

The query subjects in CDM namespaces contain predefined relationships that are related to the Parent attributes. For example, the app.j2ee.J2EEDomain class has the attribute Servers of the type app.j2ee.J2EEServer[]. And the app.j2ee.J2EEServer class has the attribute Parent of the app.j2ee.J2EEDomain type. Therefore, between all compatible pairs of CDM classes, there are predefined relationships, for example:

app.j2ee.J2EEDomain [0..1] - [0..n] app.j2ee.J2EEServer
app.j2ee.J2EEDomain [0..1] - [0..n] app.j2ee.jboss.JBossServer
app.j2ee.J2EEDomain [0..1] - [0..n] app.j2ee.weblogic.WebLogicServer
app.j2ee.jboss.JBossDomain [0..1] - [0..n] app.j2ee.jboss.JBossServer
app.j2ee.websphere.WebSphereCell [0..1] - [0..n] app.j2ee.websphere.WebSphereServer

In TADDM 7.3.0.1, some query subjects in CDM namespaces are defined for non-persistent attributes of the array type. In TADDM 7.3.0.2, query subjects are defined for all attributes of the array type. Their names have the following format:

"[name of the class declaring
the array attribute]-->[array attribute name]"

. For example, the simple.SGroup class has the GroupMembers attribute of the ModelObject[] type, so the query subject is "SGroup-->GroupMembers". These query subjects contain predefined relationships between the described array attributes and all CDM classes that contain these attributes. For example, for the mentioned GroupMembers attribute, the following relationships are defined among others:

simple.SGroup [1..1] - [0..n] simple."SGroup-->GroupMembers"
simple.SBaseCollection [1..1] - [0..n] simple."SGroup-->GroupMembers"
app.biztalk.BizTalkGroup [1..1] - [0..n] simple."SGroup-->GroupMembers"
app.hacmp.HACMPResourceGroup [1..1] - [0..n] simple."SGroup-->GroupMembers"

To use attributes of the array type, you must define a relationship between an attribute of the array type and the required CDM class by using its PK_C attribute or, in case of non-persistent attribute of the array type (ModelObject[]), its Guid attribute. For example:

To create a Cognos® report that shows sys.zOS.ZReportFile objects as ZReportfiles of the sys.ComputerSystem objects, you must define a join between the following columns in IBM® Cognos Report Studio:
```
sys."ComputerSystem-->ZReportfiles".PK__ZReportfiles_C [0..n]-[0..1] sys.zOS.ZReportFile.PK_C
```
To create a Cognos report that shows app.AppServer objects as GroupMembers of the simple.SBaseCollection objects, you must define a join between the following columns in IBM Cognos Report Studio:
```
 simple."SGroup-->GroupMembers".GroupMembersGuids [0..n]-[0..1] app.AppServer.Guid
```

In many cases, there is no need to manually create joins for attributes of the array type because there are corresponding Parent attributes of the dependent objects. The Cognos model contains relationships for them. For example, you do not need to manually create joins to create a report that shows sys.FileSystem objects as FileSystems of the sys.ComputerSystem objects, because the sys.FileSystem objects have the Parent attribute that points to the sys.ComputerSystem objects.

In TADDM 7.3.0.3, and later, the Cognos model contains query items of Data Time type for all attributes of the time stamp type. For example, sys.aix.AixUnitaryComputerSystem query subject contains the following query items:

LastStoredTime of the type Int64, which points to the LASTSTOREDTIME_C column in the building block view. Example value in the column: 1445417251307.
LastStoredTimeT of the type Data Time, which points to the LASTSTOREDTIME_T column in the building block view. Example value in the column: Oct 21, 2015 10:47:31 AM.

The LastStoredTimeT query item is the equivalent of the LastStoredTime query item, only it is expressed in the Coordinated Universal Time format, instead of UNIX epoch (long integer). The query items that contain the T suffix are the time stamp equivalents of the original long integer attribute.

WebSphere® namespace: Note: WebSphere namespace is deprecated in TADDM 7.3.0.1, and later.
This view contains the primary query subjects for a WebSphere environment. You can use this data to generate WebSphere-specific reports, such as listing the properties or JVM settings of WebSphere servers. This WebSphere Server query subject is linked to the AppServer query subject contained in the shared namespace. The WebSphere cluster and WebSphere cell query subjects are linked to the AppServer cluster and J2EE Domain query subjects contained in the shared namespace.

Shared namespace: Note: Shared namespace is deprecated in TADDM 7.3.0.1, and later.
This view contains query subjects that are considered to be key classes and can be used as a bridge to join data between different namespaces. The shared namespace contains information about computer systems and collection classes. You can use this data to create inventory reports.

Business applications namespace: Note: Business applications namespace is deprecated in TADDM 7.3.0.1, and later.
This view contains query subjects for a business application, namely, Application and FunctionalGroup query subjects. The functional group query subject is linked to the shared namespace through the Collection query subject. You can use this data to create reports showing business applications and their members.

Database namespace: Note: Database namespace is deprecated in TADDM 7.3.0.1, and later.
This view contains query subjects related to database and database servers. You can use the All Databases query subject to generate general database reports rather than vendor-specific database reports. The database content is linked to the shared namespace through the AppServers query subject.

Dependencies and relationships namespace: Note: Dependencies and relationships namespace is deprecated in TADDM 7.3.0.1, and later.
This view contains query subjects that represent generated relationships and dependencies, such as IP dependencies or switch to device relationships. You can use the general purpose relationship(unlinked) query subject to create manual links when creating a report or query. The SwitchToDevice query subject joins switches to computer system objects in the shared namespace.
There are three query subjects related to server affinity. The Server query subject shows the union of all computer systems, application servers, and service objects in the database. The Affinity (target-linked) query subject, joins each affinity relationship to its target in the Server query subject. The Affinity (source-linked) query subject joins each affinity relationship to its source in the Server query subject. The server content is linked to the shared namespace through the computer system, application server, and service query subjects. You can use this data to generate a general report showing relationship between configuration items in the network.