Browse Prior Art Database

The Application of Administrative Domain Policies to CM v8 Replication

IP.com Disclosure Number: IPCOM000030460D
Original Publication Date: 2004-Aug-13
Included in the Prior Art Database: 2004-Aug-13
Document File: 7 page(s) / 227K

Publishing Venue

IBM

Abstract

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.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 12% of the total text.

Page 1 of 7

The Application of Administrative Domain Policies to CM v 8 Replication

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. Replication will result in multiple storage locations have copies of the same object. In order to implement replication there must be a way to define how the objects are to be replicated. Content Manager Version 8.2 uses replica rules to define how objects will be replicated between different storage location. The problem is deciding on a way to regulate the replica rules.

A storage location in Content Manager is made up of a resource manager and a collection . A resource manager contains one or more collections. The collection is the actual object storage entity for storing new documents into the resource manager.[Appendix A.3]

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. [Appendix A.1] 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.[Appendix A.2]

Since there are administrative domains there are restrictions on which system objects can be defined and also restrictions on who can view them . The restrictions on defining and viewing resource manager/collection tuples can be seen in Appendix A.3 and A.4. Given the presence of restrictions on other system objects when defining and viewing replication rules, which restrictions, if any, should be placed on defining and viewing replica rules?

Alternative

The easiest way to solve the problem of defining and viewing replica rules is to place no restrictions on defining and viewing replica rules . Allow any rule to be defined between any two resource manager/collection tuples, allow sub domain admins and super admins to define the rules, and allow sub domain admins and super admins to view any rule that has been defined.

Table 1 illustrates some of the permitted rules in the given alternative. Table 1 assumes the following Content Manager system: two sub domains, su...