10 IBM Content Manager OnDemand Guide
Document indexing
Document indexing is used for reports that contain logical items, such as customer name or 
number. Each of the items in a report can be individually indexed on values, such as account 
number, customer name, and balance. Content Manager OnDemand supports up to 128 
index values per item. With document indexing, the user is not necessarily required to know 
about reports or report cycles to retrieve a document from Content Manager OnDemand. 
Report indexing
Report indexing is used for reports that contain many pages of the same type of data, such as 
a transaction log. Each line in the report usually identifies a specific transaction, and it is not 
cost-effective to index each line. Content Manager OnDemand stores the report as groups of 
pages and indexes each group. 
When reports include a sorted transaction value (for example, transaction date and number), 
Content Manager OnDemand can index the data on the transaction value. This indexing is 
done by extracting the beginning and ending transaction values for each group of pages and 
storing the values in the database. This type of indexing lets users retrieve a specific 
transaction value directly.
1.3  Content Manager OnDemand server and its components
On IBM z/OS® and Multiplatforms (MP) systems, the Content Manager OnDemand server 
can be implemented as a library server and one or more object servers that are on one or 
more nodes that are connected to a Internet Protocol network. For the Content Manager 
OnDemand system overview, see Figure 1-1 on page 5.
1.3.1  Library server and object server
A Content Manager OnDemand library server maintains two sets of database tables:
/SM590000The first set of database tables contains indexes about the reports that are stored in the 
Content Manager OnDemand Archive. 
/SM590000The second set of database tables contains information about the objects that are defined 
to the system, such as users, groups, printers, application groups, applications, folders, 
cabinets, and storage sets. 
The database manager provides the database engine and utilities to administer the database. 
The library server processes client logons, queries, and print requests and updates to the 
database. The major functions that run on the library server are the request manager, the 
database manager, and the server print manager.
A Content Manager OnDemand object server maintains documents on cache storage 
volumes and an ASM. ASMs, such as Tivoli Storage Manager on Multiplatform systems, OAM 
on z/OS systems, or ASM on IBM i systems, allow hierarchical storage management 
techniques to be applied to the stored documents. An object server loads data, retrieves 
documents, and expires documents. The major functions that run on an object server are the 
cache storage manager, data loading and maintenance programs, and optionally, the ASM.
The basic Content Manager OnDemand configuration is a library server and an object server 
on the same physical system or node. This single library or object server configuration 
supports the database functions and cache storage on one system. Y ou can add an ASM to 
the single library or object server configuration to maintain documents on archive media.