text: Even though the various components can be distributed across the network, the Content 
  Manager OnDemand Instance appears as a “single system” to both the administrator and the 
  users. 
  
  **2.2.1 Configuration consideration**
  
  The basic Content Manager OnDemand configuration is to install the library server and object 
  server on the same machine. This design is the default and most common configuration. 
  However, under certain conditions, it might be beneficial to distribute the library server, the 
  object server, and the load process to different systems. 
  
  Consider the following information to help you decide whether to run one or more of the load 
  processes on one or more separate systems: 
  
  (cid:2) Reducing system resource (processor or memory) consumption competition on the library 
  and object server system. 
  
  (cid:2) Reducing the network traffic time by running the load process on the system on which the 
  load data is created. 
  
  (cid:2) Better performance for a certain index or load process to run on another system. 
  
  (cid:2) More convenient to operate and manage the data because the data is in a smaller set. 
  
  The considerations for separate object servers are listed: 
  
  (cid:2) Distributing the workload among multiple systems. 
  
  (cid:2) Distributing the data storage among multiple systems. 
  
  (cid:2) Storing the data closer to where it will be accessed from. For example, your main 
  
  operations (library server and object server) are in the US but many of your users are in 
  China and France. You can install an object server in France to keep French data and 
  another object server in China to store Chinese data. The original object server can 
  remain in the US where the US data is kept. 