IBM FileNet P8, Version 5.2.1            

Overview of IBM FileNet CFS for Content Integrator

The primary components in an IBM® FileNet® Content Federation Services for Content Integrator system are the exporter, the importer, the Federator database, and the Federation Administration application.

The following diagram illustrates the content federation architecture:

This diagram illustrates the IBM FileNet Content Federation Services for Content Integrator architecture and process flow

Based on the rules that you define in the Federator Administration application, the exporter builds a list of documents to federate from the external repositories that are accessed through IBM Content Integrator. The exporter generates federation requests for these documents and adds the requests to the queue in the federation database. The importer processes the requests and federates the specified documents into a Content Platform Engine object store.

The Federator database contains a set of tables that are used exclusively by the exporter, a set of tables that are used exclusively by the importer, and a set of queue tables that define the interface between the exporter and importer. The Federator database can be on any accessible server.

The exporter performs the following tasks:

You can configure multiple exporters to enhance performance. You can install another instance of the exporter by extracting the CFS_HOME\fed_exporter.zip file to a different computer.

The importer performs the following tasks:

The Federator database stores the following information:



Last updated: October 2015
cfs_arch.htm

© Copyright IBM Corporation 2015.