Parameter

Required

Description

Name

Yes

Name of the repository manager.

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.

Use a prefix that makes clear that this repository is not part of the standard installation.

Active

No

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

Hide in Root Folder

No

Specifies whether 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

Identifiers of the repository services you want to use with the repository.

Selection is not necessary because this repository manager should not be used for production purposes.

ACL Manager Cache

No

Cache identification 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 (see Caches).

Windows Landscape System

No

Windows system specification that is defined in the KM system landscape.

Only necessary if the repository is operated in the persistence modes FSDB or DBFS.

Not required for CM repository managers on UNIX.

Send Events

No

Specifies whether 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 in order to use services such as the subscription service.

Persistence Mode

Yes

Selection of persistence mode for CM repository manager.

Defines where the namespace, content, and metadata are stored.

Copy the entry from the configuration of the CM repository manager to be connected.

If the database mode (DB) is specified, do not specify the Root Directory and Root Directory for Versions parameters, since they apply only to repositories that use the file system. Refer to the table below.

Cache

No

Selection of cache to be used for the CM repository manager.

The cache stores the names of resources, and properties and locks. No content is stored in the cache.

Cache for small content (<32KB)

No

Selection of cache to be used for content smaller than 32 KB.

Database Password

Yes

Specification of the database password for a valid database user with read permission.

Re-Enter Database Password

No

Enter the password again.

Database User

Yes

Specification of a valid database user with read permission.

JDBC Driver Class

Yes

Java class of the JDBC driver to use.

If you are using an MS SQL database: com.sap.portals.jdbc.sqlserver.SQLServerDriver

If you are using an Oracle database:

com.sap.portals.jdbc.oracle.OracleDriver

JDBC Connection URL

Yes

The JDBC URL that identifies the database server.

Copy the entry from the configuration of the CM repository manager to be connected and change the host name and database name if necessary.

If you are using an MS SQL database: jdbc:sap:sqlserver://<dbserver>:
<dbport>;MaxPooledStatements=150;DatabaseName=
<dbsid>;SelectMethod=cursor

If you are using an Oracle database: jdbc:sap:oracle://<dbserver>;
SID=<dbsid>;PortNumber=<dbport>;
MaxPooledStatements=150

Repository ID in Database

Yes

Identifier of the repository in the database.

Copy the entry from the configuration of the CM repository manager to be connected.

Root Directory

No

This parameter is only needed if the Persistence Mode parameter is set to FSDB or DBFS.

Specify the path to the root directory in the file system in which the data for the repository manager to be connected is stored. This can be a directory on the local server (for example /backup/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.

Root Directory for Versions

No

The path to the root directory in the file system that is used to store versions.

This parameter is only needed if the Persistence Mode parameter is set to FSDB.

Specify the path under which the version information for the CM repository manager to be connected is stored.

This cannot be the path specified in Root Directory or any of its subdirectories.

If permissions have been assigned for the current version of a document, these are passed on to previous versions of the document.