text: **Windows ActiveX API**
  The Windows client ships an ActiveX control, which can be used in its own application for 
  accessing Content Manager OnDemand servers and documents through the functions that 
  are provided by the Windows client. It is a development API that enables the development of 
  custom applications that use an installed Windows client as the API provider. The ActiveX API 
  covers only a basic operation subset. 
  
  For more information about the Windows client-based API, see*Windows Client*
  *Customization Guide*, SC19-3357. 
  
  **Structured API on z/OS**
  In z/OS environments, Content Manager OnDemand includes Structured APIs that provide 
  custom applications in CICS, IBM IMS™, TSO, or batch environments with the ability to 
  connect to Content Manage OnDemand servers. The Structured APIs support only the basic 
  read operations (log on, open folder, search, and retrieve documents and annotations). 
  
  Structured APIs are handled by a dedicated component of Content Manager OnDemand that 
  is called*MidServer*. MidServer relies on ODWEK and its API to access the Content Manager 
  OnDemand server. 
  
  Structured APIs are available only on z/OS, and they are called from COBOL or C 
  applications in the same manner as MVS calls. Because ODWEK is used as the access path 
  to the Content Manager OnDemand server, the Structured APIs can be used to access 
  non-z/OS Content Manager OnDemand servers, as well. 