IBM FileNet P8, Version 5.2.1            

Orphaned properties on Content Platform Engine

Properties are not deleted from Content Platform Engine when federated content is deleted from FileNet® Image Services.

Symptoms

When you delete federated content from FileNet Image Services, properties are not deleted on Content Platform Engine.

Causes

A document or class of documents can be captured on Content Platform Engine and federated directly to FileNet Image Services without storing the indexing properties in the FileNet Image Services index database.

If you delete the federated document by using the FileNet Image Services system, the content is deleted from the FileNet Image Services system. However, because there is no indexing information in the index database, a deletion request cannot be sent to Content Platform Engine. The properties on Content Platform Engine remain, but represent nonexistent content on the FileNet Image Services system.

This problem can also occur if you created a Content Platform Engine document with the default storage area set to the FileNet Image Services fixed content device. The new document information is stored in two surfaces on the FileNet Image Services server. The first surface stores the content of the Content Platform Engine document and has a different document number than the FileNet Image Services document. The second surface stores the FileNet Image Services document class and family that is mapped on Content Platform Engine. If you erase the document class or family information from the FileNet Image Services system, the document properties are not deleted from Content Platform Engine.

Resolving the problem

To resolve this situation, you must manually delete the orphaned document properties from Content Platform Engine.



Last updated: October 2015
p8pco041.htm

© Copyright IBM Corporation 2015.