text: **Native library dependency**
  Because of the nature of the Content Manager OnDemand architecture, ODWEK requires the 
  use of native libraries. 
  
  In addition to the physical presence on the system, Java applications must be aware of the 
  native libraries. The ODWEK native libraries are loaded as shared memory objects and 
  cannot be reloaded multiple times. If you run multiple ODWEK applications in one web 
  application server, consider this restriction. 
  
  For a description of how the native library reference is managed for the ODWEK client in IBM 
  Content Navigator in IBM WebSphere Application Server, see “Accessing the native libraries” 
  on page 195. 
  
  **ODWEK web client design considerations**
  When you design a web client for Content Manager OnDemand that is based on ODWEK, 
  consider the following items: 
  
  (cid:2) Dependency on a native shared library affects deployment and general options, such as 
  the message language, which can be set only for the whole environment. 
  
  (cid:2) Be careful with multithreading document access. Access to a single session with the 
  Content Manager OnDemand server must be in a single-threaded fashion. Only one 
  thread can access objects of a specified Content Manager OnDemand session at a time. 
  
  (cid:2) Every session that is established with a Content Manager OnDemand server consumes 
  
  memory on the ODWEK system. For high-usage applications that support many 
  concurrent users, for example, web clients that work with non-named users, we suggest 
  the use of connection pooling. 
  
  (cid:2) Ensure that a timeout concept is implemented in your application that meets the Content 
  Manager OnDemand user activity timeout. Sessions that do not time out might lead to 
  memory leaks or high memory consumption on the Content Manager OnDemand and 
  ODWEK machines. 