The following diagram shows the tree of lower-level Teradata directory objects that are children of the cn=systemone object shown in Teradata Schema Objects in the DIT Hierarchy. The overall structure of the DIT implies that a similar tree also exists under the systemtwo object.
The structure of the sub-trees contained by the tdatRootNode (cn=tdat) is rigid and must appear in the directory exactly as shown.
where:
| Row | DN | Object Class | Description |
|---|---|---|---|
| Top | cn=systemone | tdatSystem | The name of a Teradata Vantage system to which directory users can connect. |
| Middle | cn=users | tdatContainer | Teradata directory object that contains user objects |
| cn=roles | Teradata directory object that contains role objects | ||
| cn=profiles | Teradata directory object that contains profile objects | ||
| cn=ipfilters | Teradata directory object that contains IP filter objects | ||
| Bottom | cn=bwq | tdatUser | Vantage username |
| cn=jcm | |||
| cn=profile1 | tdatProfile | Vantage profile name | |
| cn=profile2 | tdatProfile | Vantage profile name | |
| cn=adminrole | tdatRole | Vantage external role name | |
| cn=userrole1 | |||
| Bottom (continued) | cn=ipfilter1 | tdatIPFilter | IP restriction filter name |
| cn=ipfilter2 |
The Teradata directory schema extensions define the object class.