IBM FileNet P8, Version 5.2.1            

Avoiding duplicate content on FileNet Image Services

Federated content might be stored twice with different document IDs.

Symptoms

The default behavior of bidirectional replication might cause document content to be duplicated on the FileNet® Image Services system. The same content might be stored twice with different document IDs if the default Content Platform Engine storage for the Content Platform Engine document class is set to Image Services and the document is also replicated to FileNet Image Services.

Resolving the problem

You can create a trigger file that is named cfs_avoid_duplicate_content to avoid duplicate content on the FileNet Image Services system. If this trigger file exists, the replication process from Content Platform Engine to FileNet Image Services verifies that the content is not already stored on the FileNet Image Services system. Duplicate content is not stored again. The replication forces the DOCTABA entry on FileNet Image Services to reference the same content.

To create the trigger file:
  • On UNIX FileNet Image Services servers:
    1. Log on as a user with root privileges.
    2. Change to the /fnsw/local/trigger directory:
      cd /fnsw/local/trigger
    3. Create an empty file named cfs_avoid_duplicate_content.
      touch cfs_avoid_duplicate_content
  • On Windows FileNet Image Services servers:
    1. Log on as the Administrator user.
    2. Open the \fnsw_loc\trigger folder.
    3. Use Notepad to create an empty file named cfs_avoid_duplicate_content.

Be aware that using this feature has some consequences. When a document is initially created, the system tags the content as "native P8" content. When this document is replicated with the cfs_avoid_duplicate_content trigger file in place, the document is no longer just a native P8 document. However, the "native P8" tag on the content is not updated. The FileNet Image Services disaster recovery tools, such as document import, ignore the "native P8" content. Hence, if the cfs_avoid_duplicate_content trigger file exists, the FileNet Image Services disaster recovery tools are not able to recover these specific documents.



Last updated: October 2015
p8pco008.htm

© Copyright IBM Corporation 2015.