372 IBM Content Manager OnDemand Guide
If the option to automatically federate is not set, data still can be federated by using the 
Windows client, ODWEK Java APIs, or ARSDOC. Figure 17-5 shows where you can select an 
option to federate selected metadata to FileNet P8.
Figure 17-5   Selecting Content Manager OnDemand documents to become records
17.3  Content Federation Services for Content Manager 
OnDemand architecture
Content Federation Services is based on the federation implementation strategy for 
managing distributed content. The distinguishing feature of this strategy is the global catalog. 
The global catalog is a searchable database that contains information about content that is 
stored in various repositories and repository types in separate locations throughout the 
enterprise that are identified for federation. Enabling Content Federation Services for Content 
Manager OnDemand does not change the architectural design of Content Manager 
OnDemand. Content Federation Services for Content Manager OnDemand is a mid-tier 
process that enhances your ability to manage content more efficiently. 
Figure 17-6 on page 373 shows the high-level access path to declare records from Content 
Manager OnDemand, Content Navigator, and Content Manager OnDemand clients.