Skip to Content

How to Create a CM Repository Manger (Persistence Mode FSDB):

CM repository managers can be set up in with different persistence modes (DB, FSDB and DBFS). In this example, we will cover how to create a CM Repository Manager with the persistence mode of FSDB. Please see the help documentation for more detailed information on which persistence mode fits your requirement when creating your CM repository manager. Of course, there are pro’s and con’s for each persistence mode and each needs to be evaluated by your organization.

There are a few things that need to be configured before creating a new CM repository manager.

1. File share – Typically companies already have an existing file share that they may want to bring into KM. Under this file share, create a directory called “Root” and another directory called “Versions”.

2. Configure a Network Path. This is necessary if you would like to have documents from a remote system available within the Knowledge Management platform. The information provided in this configuration step will allow the remote system to be accessed.

System Administration -> System Configuration -> Knowledge Management -> Configuration -> Content Management -> Global Services -> Network Path

image

3. Configure a new cache. For new repository managers that you set up, a new cache should be created. A memory caches are used to store the data in main memory. Persistent caches are used to store the data in a file system. For our repository manager we want to create a memory cache.

System Administration -> System Configuration -> Knowledge Management -> Configuration -> Content Management -> Utilities -> Caches -> Memory Cache

The parameters specified are dependent on the size and use of your repository.

image

4. Configuring a new CM repository manager (Persistence Mode FSDB)
CM repository managers can be created in different persistence modes. In our example, we are using the persistence mode FSDB. In this case, the metadata is stored in the database and the folders and documents are stored in the file system.

Please see the KM Administration Guide for more information on the other persistence modes available and which mode is best suited for your CM repository manager.

System Administration -> System Configuration -> Knowledge Management -> Configuration -> Content Management -> Repository Managers -> CM Repository

The following fields should be configured:
Name – This is the name of your CM repository manager

Description – This is a optional field that describes your CM repository manager.

Prefix – This is a user defined URI prefix that is used for this repository manager.

Repository ID in Database – This is a user defined ID that must be unique. This is used as an identifier of your repository in the database.

Root Directory – This parameter must be maintained for FSDB or DBFS CM repository managers. It defines the path to the root directory in the file system that your repository manager is assigned to.

Root Directory for Versions – This parameter defines the path to the root directory in the file system which is used to store versions of your documents if versioning is turned on.

Windows Landscape System – Here you specified your network path you defined earlier. Note: This is not necessary for CM repository managers on UNIX.

Active – This field should be check to activate your repository manager.

Internal Links Default To Dynamic – This is an optional field that if activated will dynamically create or delete links.

Send Events – This is an optional field. If activated for your repository manager, send events will occur. This needs to be activated if the subscription service is used for your repository manager.

Persistence Mode – Select the persistence mode FSDB for your repository manager. This defines where the namespace, content, and metadata are stored.

Property Search Manager – Select the property manager “CM Property Search Manager”.

Compress content greater than – Take the default value of -1. This specifies that content greater than -1 is stored in compressed form.

Repository Services – Select the repository services you want to use with your repository manager.

ACL Manager Cache – This parameter is required if an ACL security manager is specified in the Security Manager field for your repository manager. This should be set to ca_rsrc_acl.

Cache – This is the cache that should be used for your CM repository manager. Select the cache you created earlier.

Cache for Small Content (32 KB) – This field specifies the cache to be used for content smaller than 32 KB.

Connection Pool – This specified the JDC connection pool for the database. For CM repositories, use the connection pool dbcon_wcmdb_cm.

Security Manager – This parameter specifies the security manager that controls the access to the content of your repository. Typically, the Security Manager “AclSecurityManager” is used for CM repositories.

For more details of the different parameters and their values, please see the KM Administration Guide

image image
After saving your repository manager, voila! You should see your repository listed in the explorer iView. Menu path: Content Administration -> KM Content -> root.

Please note: This is based on an EP 6.0 system.

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply