Chapter 17. Content Federation Services for Content Manager OnDemand and IBM Enterprise Records 371
Figure 17-4   Defining permissions to enable CFS-CMOD 
17.2.5  Federating document metadata to Content Federation Services for 
Content Manager OnDemand
Two steps are required to federate Content Manager OnDemand documents to FileNet P8:
1. Mark the documents by using the Conten t Manager OnDemand Windows Client, ODWEK 
Java APIs, or ARSDOC. If the option to federate documents automatically is set, the 
documents are marked automatically when they are loaded.
2. Push the metadata of the documents to FileNet P8 by using the Content Federation 
Services for Content Manager OnDemand Exporter utility. 
For more information about this task, see 4.5.4, “Configure and run the CFSOD exporter 
utility”, in Federated Content Management: Accessing Content from Disparate Repositories 
with IBM Content Federation Services and IBM Content Integrator, SG24-7742.
Important: After you push the document metadata by using the Content Federation 
Services for Content Manager OnDemand Exporter utility, you must not change the 
application group ID or application ID of the Content Manager OnDemand source. They 
are part of the document identifier of the virtual document that was created in FileNet 
P8. As the result, the previously federated document’s content is no longer accessible 
from FileNet Content Platform Engine.