text: **Syst em A** **Syste m B**
  
  *Figure 12-4 Horizontal and vertical scaling with multiple LPARs*
  
  This scenario is in organizations with large systems, such as AIX or z/OS, that are installed 
  and that have enough available capacity to support the required Content Manager 
  OnDemand workload. One advantage of this configuration is that you can control the priority 
  of work and computer resource distribution to each of the LPARs, such as the number of 
  processors or the processing priority (depending on the computer system/operating system 
  architecture) that is allocated to each of the LPARs. So, for example, load jobs can be 
  assigned a low priority during the day when the focus is on data retrieval and a high priority 
  during the night when the focus is on data loading. 
  
  This setup supports horizontal scalability by using multiple technologies as appropriate. The 
  main constraint is that clients must have access to all systems through TCP/IP. 
  
  **12.2.6 Multiple server configuration rules**
  
  The following general rules apply when you configure multiple Content Manager OnDemand 
  servers. In all cases, for additional guidance, see the appropriate Content Manager 
  OnDemand documentation or contact Content Manager OnDemand Lab Services. 
  
  (cid:2) Each Content Manager OnDemand server has its own set of configuration files. 
  
  (cid:2) The parameters in all configuration files must be set so that all of the servers are part of 
  the same instance. 
  
  (cid:2) The Content Manager OnDemand clients connect to the IP address listening port of the 
  Content Manager OnDemand server (library server module). 
  
  (cid:2) The documents are retrieved from the various object servers based on the location 
  
  information that is returned by the library server. This retrieval is transparent to the client 
  systems. 
  
  (cid:2) Parallel load processes must have separate temp directories. 