Sunday, February 06, 2011

FileNet Content Services Concepts - Part 1

The Library System
Content Services (also called the library system) provides server-based enterprise content management (ECM) that can be accessed via a client interface using applications such as FileNet IDM Desktop or FileNet Web Services. An enterprise, especially if it's spread across various sites, may have multiple library systems, depending upon sizing and load balancing considerations.
A typical Content Services installation comprises the following components:
• One or more library systems.
• One or more administrative clients.
• One or more ECM clients (such as IDM Desktop).
• One or more application solutions (such as FileNet Web Services for intranet/internet access).
As you can see in the following illustration, each library system has a set of sub-components that you install and configure to provide the services for your various client-based users.


Each library system acts as an information storehouse.
·         The Property Manager stores and manages object properties (users, groups, system, and custom properties) and metadata describing your catalogued documents.
·         The Storage Manager stores the actual documents and process requests.
·         The Content Search Manager provides document content-based indexing and searching capabilities.
·         CS Replication Services, which allows you to replicate documents across multiple library systems.
You have the option to locate your database on a standalone property server. In this configuration, the initial Storage Manager, Content Search Manager, and Replication Services would be located not on the property server, but on the initial storage server.

Protected Items
When you add a document to a library system, you usually add it as a protected item. It is called “protected” because the library system physically stores the document, thereby protecting it from unauthorized access, inadvertent removal, and more. Protected items can be documents that were created by any application (for example, word-processing documents, financial spreadsheets, images, audio, tables, and so on).

Unprotected Items
A library system also lets you control and manage unprotected items (external documents), which are items that are not physically stored in the library system but are tracked for easy management. This capability is especially useful for items that are stored in special locations, yet still require version tracking or controlled access. Some examples are: magnetic tapes, printed technical manuals, printed engineering drawings, and software source code listings. Although the unprotected items added at most sites represent these kinds of physical objects, unprotected items can also be electronic files that you do not want to store in the library system.

3 comments:

Web Page Scraping said...

Hi Friends,

Very good site you have created. Content services include creating and developing content is one of most important activity of advertising services. Thanks for sharing with us...

kumaran said...

Hi,
My requirement is migration task from CSv5.5 to IS 4.
What is the best approach to do this migration task?
I having idea of using idm desktop api's. However it's little slow.
Any ideas/Comments are welcome.

Thanks & Regards,
kumaran

Manjeet Singh Wadhwa said...

We had created our Tools for data and content extraction in .net and divided the whole migration in to various phases. We used IDM Desktop APIs for the same. I am afraid as I am not aware of any other tool .