text: **6.4 API access**
  
  An important component of Content Manager OnDemand is the Content Manager 
  OnDemand Web Enablement Kit (ODWEK) Java APIs. These APIs are used to build 
  applications that access the Content Manager OnDemand server. Various applications can 
  be built by using the APIs. Examples of applications include IBM Content Navigator (ICN) and 
  CMIS. By using the ODWEK APIs, you can also build your own application server or web 
  services applications. 
  
  All of these types of applications address the following situations: 
  
  (cid:2) Users communicating and interacting with a mid-tier, custom-built access mechanism that 
  controls access to the Content Manager OnDemand server. For example, the mid-tier 
  application can control whether a Content Manager OnDemand user request is accepted 
  or rejected, and if it is accepted, which Content Manager OnDemand server the request is 
  routed to. 
  
  (cid:2) The network transmissions between the ODWEK Java APIs and the Content Manager 
  
  OnDemand server use a proprietary Content Manager OnDemand protocol and optionally 
  can be encrypted by using SSL. 
  
  (cid:2) The network transmissions between the mid-tier custom application and the users can 
  optionally be encrypted by using SSL. 
  
  (cid:2) By using an optional user proxy implementation, multiple users can share a user ID and 
  password, therefore reducing the number of actual logons to the Content Manager 
  OnDemand server while maintaining secure access to the system through the 
  custom-built access mechanism. 
  
  (cid:2) The Java APIs can pass a security token through to the Content Manager OnDemand 
  
  server. This token can then be captured by the security exit and the exit can perform the 
  required special processing. 