IBM FileNet P8, Version 5.2.1            

Defining FileNet Image Services document classes and index properties

Define the FileNet® Image Services document classes and index properties that you plan to map to Content Platform Engine document classes and properties.

About this task

The document class is the basis of connecting Content Platform Engine to the FileNet Image Services content storage area. Documents created by IBM® FileNet P8 applications are assigned the security and the family of the appropriate FileNet Image Services document class according to the specified class mappings.

Use the FileNet Image Services Database Maintenance application to create one or more document classes for Content Platform Engine documents. Create a separate FileNet Image Services document class for each type of document that you want cataloged on Content Platform Engine. Another way to organize the data is to create separate document classes for documents that are captured by each IBM FileNet P8 application that stores content in FileNet Image Services and by each Panagon or other application that runs on the Image Services system.

Tip: Define a new media family on FileNet Image Services for federated documents to help organize your data and track document classes.

If the documents in a document class are to be captured and cataloged by the Content Platform Engine server only, set the Enable Cataloging option to No. Do not configure index properties for this document class. Documents that are added to the document class are federated and the metadata is copied to Content Platform Engine, but no record of the document is stored in the FileNet Image Services index database after the import is complete. Therefore, you cannot retrieve the document, or even see the document reference with a query, by using FileNet Image Services such as Integrated Desktop Management.

If the documents in a document class are to be captured on the FileNet Image Services system, you have two choices:
  • If you want to retrieve the documents from only the Content Platform Engine server, set the Enable Cataloging option to No. Configure index properties for the document class so that the properties can be exported to Content Platform Engine. The documents are not retrievable from FileNet Image Services.
  • If you want the ability to retrieve the documents from both Content Platform Engine and FileNet Image Services, set the Enable Cataloging option to Yes. Index properties for this document class are then cataloged on both Content Platform Engine and FileNet Image Services.
Important: Documents that are not cataloged on the FileNet Image Services system cannot be retrieved by FileNet Image Services applications.
Tip: If you configure inbound replication, by which Content Platform Engine properties are synchronized with FileNet Image Servicesproperties, and a document is cataloged on both FileNet Image Services and Content Platform Engine, do not update the properties on Content Platform Engine.

If you update the Content Platform Engine properties, Image Services does not update the corresponding properties, and the properties on the two systems are now out of synchronization. If the properties on the Image Services system are then re-exported to the Content Platform Engine system, the Image Services properties overwrite the updated Content Platform Engine properties. If the properties on the Image Services system are updated through an application such as IDM Desktop or Image Services Toolkit, the update on the Content Platform Engine system fails because the Content Platform Engine properties do not match the expected value.



Last updated: October 2015
cfsic008.htm

© Copyright IBM Corporation 2015.