The Application of Administrative Domain Policies to CM v8 Replication
Original Publication Date: 2004-Aug-13
Included in the Prior Art Database: 2004-Aug-13
New to Content Manager Version 8.2 is replication. Replication is the ability to replicate, or copy, an object from one storage to another storage location. The problem is deciding on a way to regulate the replica rules. A replica rule takes two parts. The first part is the source resource manager/collection tuple which has the original object that will be copied. The second part is the target resource manager/collection tuple which is where the object will be copied to. A source resource manager/collection tuple can have many targets, meaning the same object will be copied to many different places. The problem with regulating replica rules is caused by the presence of administrative domains in Content Manager. Administrative domains streamline and distribute management of information. There are two types of administrative domains: the public domain and sub domains. The public domain is available to all users while sub domains have restrictions on who can use them. Each sub domain may have a sub domain admin. A sub domain admin is a user who has administrator privileges only for that sub domain. This is different from a super admin. A super admin is a user who has administrator privileges for all system objects, regardless of domain while a sub domain admin can only manage system objects in their own domain. The solution implemented by Content Manager Version 8.2 allows for only a subset of the possible combinations of resource manager/collection tuples to be replica rules based on domains. Also, while super admins can define any of these rules and view any of these rules the sub domain admins may not. The sub domain admins may only view replica rules that involve their own domain or the public domain and may not define replica rules where the source is either in the public domain or in a different sub domain.