Filtered Replicas and DirXML
Articles and Tips: tip
01 Oct 2000
One of the new features of NDS eDirectory 8.5 (the "Tao" release) is the ability to select and filter which data gets replicated in specific locations. This feature can be used with DirXML to integrate applications on a distributed network. Some applications may assume that all the data needed is centralized and may not be able to access data that is stored on separate replicas. Using a set of filtered replicas creates a global view of the NDS data, allowing only the data you are interested in to be stored and synchronized on the application server.
To start this process, first create a replica filter that describes the desired attributes to be stored on the server. Next, define the partition scope to specify the set of desired partitions that will contain the target data. Filtering can be applied to inbound or outbound data synchronization. To do this, ConsoleOne provides the mechanism to define the scope and filter.
DirXML benefits from (but does not require) filtered replicas by greatly reducing the number of events that the DirXML engine has to process. Setting up the filters to include only the objects and attributes that an application requires results in a partition replica that contains only the data that you need. This reduces disk space usage, generates less network traffic, and decreases the time it takes to conduct database searches.
* Originally published in Novell AppNotes
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.