Content federation considerations for Content Services
repositories
There are several considerations to take into account when you federate documents from
IBM®
FileNet® Content Services repositories.
Configuring Content Services
To configure Content Services as a source repository for
content federation, configure the maximum cache size and the maximum cache document.
Deleting federated documents
When a version of a document that was federated from a Content Services repository is deleted from a Content Platform Engine object store, a spiVersionErase request is automatically sent
to the source repository to delete the corresponding source version.
Archived document and record declaration Content Services repositories can archive older versions of
documents. Because version archival causes content to become temporarily or even permanently
unavailable, archived documents cannot be locked down and thus cannot be declared as
records.
Security changes in Content Services after record declaration
After a federated document is declared as a record, the Lockdown Principal is granted
Admin level access rights to the source document in Content Services. In
additon, users and groups that have Admin or Owner level access rights to the source document are
granted Author level access. They are granted Author rights instead of View rights so that users can
create a new version of the document but cannot modify its properties.
Testing Content Services rules
After you configure rules for Content Services, you can test
how many documents a query returns by running an equivalent search from IDM Desktop.