IBM FileNet P8, Version 5.2.1            

Setting up Content Federation Services for Image Services

To set up Content Federation Services for Image Services, you must first configure the FileNet® Image Services system to work with the content federation system. You then configure communication between Content Platform Engine and FileNet Image Services, map the document classes and properties between the two systems, and configure the FileNet Image Services export tool to federate documents to Content Platform Engine.

Before you begin

Install FileNet Image Services, the Remote Admin Console, and Content Platform Engine on the appropriate servers. Because Content Federation Services for Image Services is a component of Content Platform Engine, no separate installation is necessary.

About this task

When the tasks on the FileNet Image Services system are finished, the FileNet Image Services system administrator must provide the following information to the Content Platform Engine system administrator:
  • IP address of the FileNet Image Services server.
  • Three-part domain name of the FileNet Image Services system.
  • Server name of the FileNet Image Services Root/Index server.
  • Content Federation Services for Image Services administrative user name.
  • Names of the document classes and index properties to be used with content federation

Procedure

To configure Content Federation Services for Image Services:

  1. Verify the TCP/IP parameter settings on all Windows servers.
  2. Configure the FileNet Image Services system:
    1. Create a Content Federation Services for Image Services administrative user.
    2. Optional: If you plan to use IBM® Enterprise Records with Content Federation Services for Image Services for federated record management, create a records administrator group and configure record management security.
    3. Define document classes and index properties..
    4. Configure the federation of annotations.
  3. Configure the Content Platform Engine server:
    1. Configure communication between Content Platform Engine and FileNet Image Services.
    2. Create an object store.
    3. Create an IBM FileNet Image Services fixed content device for each FileNet Image Services server that needs to communicate with Content Platform Engine. For the User field, specify the name of the Content Federation Services for Image Services administrative user that you defined on the FileNet Image Services system.
    4. Create a fixed storage area for each FileNet Image Services fixed content device.
    5. Create an external repository for IBM FileNet Content Federation Services for Image Services. In the domain navigation pane of the Content Platform Engine administration console, click Global Configuration > Administration > External Repositories and click New.
    6. Create a replication group to associate the external repository with the object store.
    7. Create the Content Platform Engine document classes and properties that you plan to map to the FileNet Image Services document classes and index properties.
    8. Define document class and property mappings between Content Platform Engine and FileNet Image Services.
  4. On the FileNet Image Services Remote Admin Console workstation, enable the federation of new and existing documents.
  5. Optional: If the FileNet Image Services and Content Platform Engine servers are in separate physical locations, configure remote caching to improve performance.


Last updated: October 2015
cfsic076.htm

© Copyright IBM Corporation 2015.