IBM FileNet P8, Version 5.2.1            

IBM FileNet Content Federation Services for Content Integrator

IBM® FileNet® Content Federation Services for Content Integrator federates documents from multiple repositories, including IBM Content Manager, IBM FileNet Content Services, Documentum Content Server, and Open Text Livelink Enterprise Server.

The following diagram illustrates the IBM FileNet Content Federation Services for Content Integrator architecture.Diagram showing the IBM FileNet Content Federation Services for Content Integrator architecture and process flow

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.

An administrator can use the Federator Administration application to create rules that specify the criteria by which documents from the external repository are selected for federation. The exporter finds the documents that match the criteria and queues an import request for each document in the federator database. You can run multiple Exporter processes to improve performance. The importer creates or updates federated documents for each import request.

The federator database stores the following information:
  • The metadata of the documents from the external repository that are queued for federation.
  • Federation status and time stamp information for batches and for individual items.
  • Content federation configuration items, including logging levels, and the content integration server authentication credentials.
  • Content federation rule information, including the constructed queries (that form part of a rule), target Content Platform Engine folders (required in each rule), and records declaration options.
  • A record of documents that were federated and which object store they are federated to.


Last updated: October 2015
p8sov116.htm

© Copyright IBM Corporation 2015.