Show TOC

Light CM Repository ManagerLocate this document in the navigation structure

Definition

The Light CM repository manager is a lightweight CM repository that offers a subset of the CM repository manager functionality with improved performance. For more information about the CM repository manager, see CM Repository Manager .

In particular, the Light CM repository manager offers:

  • DBFS persistence mode

  • CM functions for working with documents and folders (create, read, update, delete, copy, move, and rename)

  • Basic versioning

  • Permissions based on ACL Security Manager. For more information, see ACL Security Manager .

  • Use of KM repository services

  • Use of the AS Java cache management system (cluster-wide cache)

The Light CM repository manager does not offer the following features that are available in the CM repository:

  • DB and FSDB persistence modes

  • File system content cache

  • Advanced versioning, as defined in the WebDAV standard

  • Flexible links, for more information, see Use of Links

  • Own property search (use of generic property search provided by repository framework)

Prerequisites

You have installed a database for storing metadata.

For an overview of supported databases, see SAP Service Marketplace at Start of the navigation path service.sap.com/platforms  Next navigation step Product Availability Matrix End of the navigation path.

Resource Properties

The Light CM repository manager supports the entire spectrum of standard resource properties, including Description, Read-only, and Hidden. The default value of the Description property is blank, and the default value for Read-only and Hidden is 'false'.

Restrictions for Resource Property Names

Only letters or underscore are allowed as the first character of a resource property name.

Namespace Restrictions for Resource Names

  • Maximum length of resource names:

    448 characters

  • Maximum length of path (URI without prefix):

    No restriction

  • Permitted characters in resource names:

    All Unicode characters allowed by repository framework, but restrictions may exist for some components of the repository framework.

    Note

    Do not put a full stop/period at the end of the resource name.

Database Restrictions

The following restrictions apply for the database:

  • Maximum number of resources in a repository instance is approximately:

    2,147,483,648 (this number may vary depending on the folders structure and additional metadata)

  • Maximum length of large property values (string type):

    2,147,583,647 bytes (2 GB) (this number may be smaller depending on the maximum CLOB size supported by the database that is used)

Cache

The Light CM repository manager uses the AS Java cache management system, thus minimizing the performance overhead with a cluster-wide caching. For more information, see Cache Management System

Cache Configuration

The following table lists the cache regions in the Cache Management Library used by the Light CM repository manager:

Cache Region Name

Cache Region Description

Cache Region Content

KCFRegion-Nodes

KCF Cache Region For Nodes

Nodes

KCFRegion-RIDs

KCF Cache Region For RIDs

RIDs

KCFRegion-IDs

KCF Cache Region For IDs

Node IDs

KCFRegion-IDsByConstIDs

KCF Cache Region For IDs by const IDs

IDs corresponding to constant IDs

KCFRegion-Collections

KCF Cache Region For Folders

Children for a folder

KCFRegion-Properties

KCF Cache Region For Properties

Properties per resource

KCFRegion-Contents

KCF Cache Region For Small Contents

Small content (up to 32k)

KCFRegion-Locks

KCF Cache Region For Locks

Resource locks

You can use SAP Management Console to monitor the Light CM repository manager cache regions. For more information, see SAP Management Console

Parameters of a Light CMRepository Manager

Parameter

Required

Description

Description

No

Description of the repository manager.

Prefix

Yes

The URI prefix for which the manager is registered. This specification is entered in the list in the root directory.

The URIs of all resources managed by this repository manager have this prefix in common. This prefix is used to identify the repository manager that is responsible for a resource with a given URI. Note that you must enter the prefix with a forward slash, for example, / <your_prefix>

Active

No

You can (de)activate the repository manager using the Active parameter.

Hide in Root Folder

No

Specifies whether or not the repository is listed in the root directory.

If you activate this parameter, the repository is not listed in the root directory.

Repository services

No

Specifies the repository services that you want to use with the repository.

Security Manager

No

Selection of the security manager that controls access to repository content.

If you want the Light CM repository manager to perform an authorization check when resources are accessed, you need to specify a security manager.

The AclSecurityManagerMi is to be used for Light CM repositories.

ACL Manager Cache

No

Specifies a memory cache for resource ACLs: ca_rsrc_acl.

This parameter is required if an ACL security manager is specified in the Security Manager parameter. The cache is already created in the standard delivery (for more information, see Caches ).

Send Events

No

Specifies whether or not the repository sends events when operations such as delete and update content are performed.

The repository sends events if this parameter is activated. This is necessary to be able to use services such as the subscription service.

Content Folder

Yes

This parameter denotes the path to the root directory in the file system to which the repository manager is assigned. This can be a directory on the local server (for example, /usr/myshare/somedir) or on a released remote server. In order for you to access a file system of another UNIX host, the directory in question must be mounted on the portal server. The repository manager is responsible for this directory and all its subdirectories.

Multiple repository managers are not allowed to share a subpath in their Content Folder parameter.

Note

For security reasons, restrict authorizations for this path specification in the file system.

Repository ID in Database

Yes

Identifier of the repository in the database. This is required because a database is used for storing the data of multiple repositories. The value must be an alphanumeric string that is unique among the IDs of all repositories that use the database. If the ID is not specified, the name of the repository is used as the ID. If you use an ID, the prefix can be changed without having to coordinate it with the database.

Do not use special characters in the ID.
Activities

To create and configure a new Light CM repository manager, or to change the configuration of an existing one, choose Start of the navigation path System Administration  Next navigation step System Configuration  Next navigation step Knowledge Management  Next navigation step Content Management  Next navigation step Repository Managers  Next navigation step Light CM Repository Manager  End of the navigation path in the portal.

Example

Light CM Repository Manager Configuration

Description

Standard Light CM repository for content

Prefix

/LightRM

Active

true

Hide in Root Folder

false

Repository Services

properties, feedback, comment, rating, accessstatistic, personalnote, discussion, tbp, statemngt, subscription, svc_acl

Security Manager

AclSecurityManagerMi

ACL Manager Cache

ca_rsrc_acl

Send Events

true

Content Folder

$(sys.global.dir)/config/cm/LightRM

Repository-ID in DB

LightRM

More Information

Backing Up and Restoring CM Repositories in DBFS Mode

CM Repository File System Check

CM Repository Database Check

Unconfigured CM Repositories