202 IBM Content Manager OnDemand Guide
If a FileNet P8 system is installed in your environment that serves as your primary content 
management system and reports need to be available to users without their knowing that 
those reports are in a different system, this integration might suit your needs. The same 
situation applies to the use of FileNet P8 Records Management, which can be applied to 
Content Manager OnDemand documents as well, therefore bringing a level of federated 
records management capability to your documents.
When you plan your integration with FileNet P8, remember this federation is active: Content 
Manager OnDemand actively publishes document links into a FileNet P8 system. Y ou must 
consider both volumes (FileNet P8 systems usually are smaller than Content Manager 
OnDemand systems) and the active federation process.
For more information about Content Manager OnDemand and FileNet P8 integration, see 
IBM FileNet Content Federation Services for Content Manager OnDemand, SC19-2711.
8.3  Client API overview
With various client options, multiple API options are available to navigate through the system 
and access Content Manager OnDemand documents. Although the Java API that is provided 
by Content Manager ODWEK is the API that is used most by clients and the basis for most 
development projects, other APIs are available and used for a limited range of scenarios.
The following list shows the APIs that are available for Content Manager OnDemand:
/SM590000Content Manager ODWEK: The Java API for Content Manager OnDemand
/SM590000SOAP and Representational State Transfer (REST) web services that follow the CMIS 
standard
/SM590000Windows OLE (ActiveX control) that is provided by the Windows client
/SM590000XML administrative API through the ARSXML server command
/SM590000Structured APIs on z/OS environments 
/SM590000The standard Content Manager OnDemand server commands that serve as a 
console-based API to work with Content Manager OnDemand documents
8.3.1  Content Manager OnDemand Web Enablement Kit
ODWEK provides a Java API to access Content Manager OnDemand servers and their 
documents. It is the strategic client API that provides the largest feature set of any Content 
Manager OnDemand API. It is used by web clients, such as Content Navigator or WEBi, by 
abstraction layers, such as Information Integrator, or by API components, such as CMIS.
The ODWEK Java API and its use to develop Content Manager OnDemand clients are 
described in detail in IBM Content Manager OnDemand Web Enablement Kit Java APIs: The 
Basics and Beyond, SG24-7646. This section covers only a basic overview and focuses on 
client considerations about ODWEK. Developers are encouraged to read the referenced book 
before they plan a client development that is based on ODWEK.
Scope
ODWEK is a Content Manager OnDemand component that can be used by all Content 
Manager OnDemand customers. It is focused on typical client use cases, such as searching 
for and accessing data that is stored in a Content Manager OnDemand archive. It also has 
web viewers, such as the line data applet and Content Manager OnDemand AFP viewer.