Configuring FileNet P8 for use with Image Services

Collector Server can access Image Services documents after you make the metadata and the annotations of the Image Services documents available in the Content Engine catalog of FileNet P8.

1. Create a FileNet P8 user that Content Collector for SAP can use to connect to FileNet P8.
2. Create a domain for the object stores, or use the default domain.
3. Create a fixed content device for each Image Services server that you want to access.
4. Create an external repository for each fixed content device.
5. Create one or more storage areas within existing object stores or create one or more object stores.

   You can select a storage area of your choice. If, however, you want to use a fixed storage area, select the fixed content device that you created.

   Add the users or group of users who must access the Image Services documents. Add at least the user that you created in step 1. If you do not specify a user, all FileNet P8 users who are not administrators can only read the Image Services documents.

6. If you use FileNet P8 Version 5.1, or later, and Image Services Version 4.2., create a replication group for each combination of object store and external repository.
   In the replication group, you specify which object store is associated with which external repository. In addition, you determine where the documents are to be cataloged:

   • If the documents are to be cataloged on both Image Services and Content Engine, select the Master mode for the object store.
   • If the documents are to be cataloged on Content Engine only, select the Slave mode for the object store.

   Note: Specific document types can be cataloged on Content Engine only. For more details, see Replication direction of the document classes.
7. Create the properties for the document classes.
   You must create all properties that are defined for the Image Services document classes. In addition, you must create all properties that Content Collector for SAP needs to archive and update documents. Otherwise, the Image Services documents can only be read or deleted.

   For an overview of the properties that you must create, see Mapping of the Image Services properties to the FileNet P8 properties: Overview.

8. For each Image Services document class, create a document class in FileNet P8, and assign the properties that Content Collector for SAP needs and the custom properties. If possible, use the name of the Image Services document class for the FileNet P8 document class.

   For each FileNet P8 document class, add the user that you created in step 1, or the group to which this user belongs, to the Default Instance Security access control list (ACL) and specify “Full Control” as permission. With this permission, the user can view, create, modify, read, and delete the Image Services documents.

   Note: If you use FileNet P8 Version 5.1, or later, and Image Services Version 4.2., ensure that no default replication group is specified for the FileNet P8 document classes that are to contain incoming documents. Otherwise, new versions of a document are automatically synchronized with Image Services. For details regarding the settings for outgoing documents, see Replication direction of the document classes.
9. Map the Image Services document classes to the FileNet P8 document classes. If you use FileNet P8 Version 5.1, or later, and Image Services Version 4.2., specify the replication direction for each document class mapping:
   • If you want to continue cataloging documents on Image Services, you must synchronize the Image Services catalog with the Content Engine catalog. In this case, you must enable bidirectional federation for each document class mapping. Select Both as replication direction.
   • If you want to keep only the Content Engine catalog up to date, select Inbound as replication direction.
   Note: The data type of the documents determines the replication direction. For more information, see Replication direction of the document classes.
10. Within each document class mapping, map the Image Services properties to the FileNet P8 properties.
    For an overview of which properties must be mapped, see Mapping of the Image Services properties to the FileNet P8 properties: Overview.

    If you use FileNet P8 Version 5.1, or later, and Image Services Version 4.2, specify the replication direction for each property mapping. The replication direction depends on the replication direction of the document class to which the properties belong. For information about which replication direction to select for the individual properties, see Replication direction of the properties.

11. For each object store or for each document class, create a storage policy where you define where the content of the documents is to be stored.
    Because the storage policy can affect the performance, use the policy that fits best your company policy and, at the same time, has the least impact on the performance.
12. Annotations of Image Services can be copied manually to the Content Engine catalog or can be cataloged at the same time as the metadata of the documents. To export the annotations together with the metadata, select the Export Annotations check box in the System Configuration Editor (fn_edit).
13. Export the metadata, and any annotations, of the Image Services documents to the Content Engine catalog.
    You use the IS Catalog Export Tool on the Remote Admin Console (RAC) workstation to perform this task.

    If you want to ensure that updates to the Image Services catalog are automatically exported to the Content Engine catalog, use the IS Catalog Export Tool to create default mappings between the Image Services document classes and the FileNet P8 object stores.

14. Enable the Content Engine catalog to be updated automatically: On the IS Import Agent page of the Enterprise Manager Properties window, select the Enable Dispatcher check box and adjust the import settings according to your needs.