286 IBM Content Manager OnDemand Guide
Examples of these configurations are illustrated in the figures in this section. These figures 
are only a sample of the possible configurations that are used to illustrate the basic scalability 
features. 
Figure 12-1 illustrates a single Content Manager OnDemand instance. In this figure, the 
Content Manager OnDemand server supports the library server, one or more object servers, 
and one or more load processes. The following sections provide examples of how the Content 
Manager OnDemand server can be scaled both vertically and horizontally.
Figure 12-1   Scalability: A single instance (simple client/server) setup
12.2.1  Vertical scalability
Y ou can scale Content Manager OnDemand vertically by expanding the system, by using a 
larger system, through application design, or through parallel archive access.
Expanding the system
Content Manager OnDemand is vertically scalable if the system that it is running on is 
scalable. Vertical scalability is achieved by adding more hardware to the system. This 
hardware might be in the form of faster processors, more processors, memory, disks, I/O, or 
network capacity. 
The limit to the amount of possible vertical scalability is the architectural hardware constraints 
of the system. For example, if the system supports only 24 GB of memory, that memory 
limitation can be overcome only by buying a larger system.
Using a larger system
Y ou can scale a Content Manager OnDemand system vertically by using a larger system in 
one of two ways:
/SM590000Installing a larger system within the same family and architecture, for example, moving 
from an entry-level AIX system to an enterprise-level AIX system
/SM590000Installing a larger system from a different architecture and family, for example, moving a 
Content Manager OnDemand server from a Windows system to an AIX system 
Cl ie nt
TC P/I P
Network
Sin gle  Sy st em
Obj ect Server
Tmp (hfs,zFS)
Cache
TSM/OAM/VSAM
Lo ad  Pr oc es s
tmp
Lib rary Server
Tmp
Cache
db2