Abstract: A configuration object is provided to configure a server. The configuration object can include storage node information for a first set of storage nodes available to a server. The configuration object determines, from the storage node information, a second set of storage nodes for inclusion in a map. The configuration object maps each storage node in the second set of storage nodes to a different index value in a set of index values. The configuration object receives an object identifier for a first object, transforms the object identifier into a resulting index value in the set of index values and, based on a determination that a first storage node is mapped to the resulting index value in the map, selects the first storage node as a target storage node for servicing a request to perform a first operation with respect to the first object.

Abstract: Disclosed is a new identifier allocation approach for allocating repository object identifiers beyond a maximum number usually allowed for a single repository. The new identifier allocation approach includes an enhanced identifier structure in which a portion usually reserved for a docbase identifier is modified to combine with a partition identifier. The actual docbase identifier is stored in a server configuration file. When the maximum number of object identifiers has been allocated, a new partition is created and a sequence table is updated with a new entry that reflects the new partition. A new repository object identifier is allocated using the docbase identifier combined with the new partition identifier. In this way, more than 4 billion objects per object type can be addressed uniquely within a docbase by creating new partitions. This new approach is very unique and flexible in accommodating both on premises and multi-tenant environments.

Abstract: Embodiments of a multitenant content server that employs embodiments of a database architecture for use in multitenant environments that includes a global partition and a tenant partition for each tenant. These partitions can be accessed using sessions corresponding to the partitions and interfaces associated with the tenants.