What is the process used by RadiantOne to Abstract Heterogeneous Data Sources to Create a Logical Federated Directory?
Objects from the underlying data stores are first converted into a common model (schema) and then linked. The schemas from the underlying sources are extracted via a wizard process from the RadiantOne Schema Manager tool. Three different sources are used in diagram 9.1 below to depict this process. Diagram 9.1: Schema Extraction Process After the schemas have been described, different virtual directory information trees can be designed using the RadiantOne Directory View Designer tool. Diagram 9.2 below depicts this process. Diagram 9.2: Directory View Designer Process Different methods can be used to link objects from different data sources. Objects can be linked through a static label (equivalent to the notion of an OU) or linked together by some common values/keys (the parent object conditions the descendant object: a child object appears only under a parent if there is a common key value with the parent object).
Objects from the underlying data stores are first converted into a common model (schema) and then linked. The schemas from the underlying sources are extracted via a wizard process from the RadiantOne Schema Manager tool. Three different sources are used in diagram 9.1 below to depict this process. Diagram 9.1: Schema Extraction Process After the schemas have been described, different virtual directory information trees can be designed using the RadiantOne Directory View Designer tool. Diagram 9.2 below depicts this process. Diagram 9.2: Directory View Designer Process Different methods can be used to link objects from different data sources. Objects can be linked through a static label (equivalent to the notion of an OU) or linked together by some common values/keys (the parent object conditions the descendant object: a child object appears only under a parent if there is a common key value with the parent object). In the case of a directory, there are two ways objects can be mounted