IBM® FileNet® Content Federation Services provides central control of enterprise content from multiple, disparate content sources through a single, unified metadata catalog. Federated content appears in Content Platform Engine as native content where it can be retrieved, viewed, used, and managed, while it remains in the source repository.
You can federate content and metadata from the following source repositories:
The federation process is managed by sets of rules and data mappings that define what information to retrieve, when to federate documents, and how to map metadata information from the source document to document property values in a Content Platform Engine object store. If the object store is configured for full-text indexing, the content of the federated documents is indexed so that text-based searches can locate the documents.
After documents are federated, they can be used with all of the standard Content Platform Engine features, including property searches, text searches, records management, and workflows. To keep data in the object store current with the data in the external repository, you can configure the frequency with which the federation process runs.
Other federation capabilities include failover, failure recovery, federation of external repository updates, federation of documents with version series, and storage of general configuration information. The content federation system can be configured for use in highly available environments.