How Collections are Replicated to Child Sites

SMS propagates collections created at a parent site to all child sites. Propagated collections cannot be modified at the child site. SMS uses a special icon for collections that were propagated from a parent site to indicate that they are locked and cannot be modified.

Child sites that are primary sites receive all the data about a propagated collection (general data, membership rules, and a list of subcollections) except for the actual membership list, which each child primary site generates for its own site. By having the primary child site generate the membership list, SMS minimizes the transmission of data and enables the membership list to be updated more easily.

Secondary child sites receive the membership lists for those resources that belong to their sites. Secondary child sites do not receive the membership rules because those sites to not maintain a site database. Whenever a collection is reevaluated at a primary site, its secondary sites receive updated membership lists that replace outdated lists.

Note    If a collection is not updated within a week, SMS automatically sends the entire collection from a primary site to its child sites to ensure that the collections remain synchronized.

Related Topics

Topic Link

About Collections

Topic Link

About Subcollections

Topic Link

Using Collections to Manage Resources Overview