16 IBM Content Manager OnDemand Guide
2.1  Introduction
A Content Manager OnDemand instance is a logical server environment. The base system 
components are a library server and one or more object servers. Optional components 
include one or more archive managers and one or more Full Text servers. 
2.2  Architecture and platform
Before you begin your installation and configuration, it is important to understand the general 
architecture of the Content Manager OnDemand server to help you determine the type of 
configuration that meets your business requirements. As illustrated in Figure 2-1, from an 
architectural perspective, the base Content Manager OnDemand server consists of two 
components: a library server and one or more object servers. The library server contains the 
database system tables and the application group data tables. The object server contains the 
stored reports and documents.
Figure 2-1   Architectural view of Content Manager OnDemand
Data is loaded and retrieved from the Content Manager OnDemand server through a network 
connection (TCP/IP). The advantages of this design are listed: 
/SM590000The instance components can be physically distributed across the network. 
/SM590000System users (client systems) can be anywhere on the network. By using the Internet, the 
clients can be anywhere in the world.
/SM590000The “load process” can run either on the library server, the object server, or on any other 
system (containing the appropriate software) that is attached by network to both the library 
and object server.
/SM590000This design also allows the library server and object servers to be placed on the same 
system (or logical partition (LPAR)) or on two (or more) systems (LPARs).
Object Server(s)
(1 or more)
Archive Storage 
TSM – OAM - ASM
Library Server (1)
Same or different machine/platform
Cache 
Storage
Temp
Storage
TCP/IP   or   No TCP/IP
Load Process
HFS
zFS (z/OS)
IFS
NFS
NAS
odbc
Architecture overview of OnDemand
Cache 
Storage
Temp
Storage HFS
zFS (z/OS)
IFS
NFS
NAS
Client
TCP/IP
Network
DB2
DB2