FileNet Content Services Concepts - Part 6

Property Manager The components in the library system that store and maintain in a database a library system's objects and properties. These objects and properties identify and describe stored documents and unstored items. They also describe users, groups, searches, and system components. Each library system has its own Property Manager. The Property Manager is roughly equivalent to the database engine, but has a slightly larger conceptual purpose. For example, each of the library systems that happens to share a database engine is said to have its own unique Property Manager.

Property repository A Microsoft SQL Server database or Oracle tablespace that contains the objects and properties for a single library system. The objects and properties identify and describe stored documents and unstored items. They also describe users, groups, searches, and system components.

The documentation generally refers to a SQL Server database or Oracle tablespace as a property repository only after you have installed the associated library system and applied its initial changes to the database or tablespace. Prior to library system installation, the documentation uses database or tablespace rather than property repository (for example, “To create an Oracle tablespace:").

Property server The server where the library system database engine is installed. Typically, this server is also the initial storage server, but under certain configurations, may be a standalone database server instead.

Storage Manager The library system service that processes operational requests (for example, to check in or check out) and stores version files controlled by the library system.

Storage category To a user, such a category typically describes a type of file (for example, Word Docs, Payroll Records, Memos). To an administrator, storage categories provide a way of controlling load balancing in the various storage repositories. Storage category names are determined by an administrator to reflect the working environment at a particular site. One or more storage categories may be assigned to a storage repository and administrators can change these assignments as load requirements change.[Can be visualize as document class]

Storage repository A storage area (that is, a directory) for specific version files controlled by the library system. Each file is stored according to a storage category, which is assigned when the file is added to the library system as a protected item. A storage repository may be assigned numerous storage categories for a particular installation of a library system.

Storage server Any server where initial or additional services for a library system are installed.

Verity K2 Master Admin The Verity component that governs all Content Search Managers for a library system.

Verity K2 Master Admin Server The server where the CS installer places the Verity K2 Master Admin that governs the Content Search Managers for a given library system.

Archive category Describes a way of handling version files that are moved offline during automatic or manual archiving. Each protected item is given an archive category (for example, Archive To Tape) when it is added to the system. Each archive category is assigned to a specific storage directory called an archive repository.

Archive repository A storage area (that is, a directory) for specific system-controlled version files that are moved offline. The archive repository is where the files are held while awaiting archive storage or destruction outside of the library system. Archive repositories can be described as reclaimable or no reclaimable. Typically, files that are moved offline through a reclaimable archive repository are more easily reclaimed for use at a later time. Each archive repository may be assigned numerous archive categories.

Content Search Manager A software service that contains the program files required to make content searching for version files available with the library system.

Content search repository A named collection of files identifying versions that have been indexed so that users can find those versions based on the actual contents of the version files. You must add at least one of these content search repositories for each Content Search Manager.