Library server

The Content Manager OnDemand library server uses a relational database manager to manage objects and provide data integrity by maintaining index information and controlling access to objects stored on one or more object servers.

The library server directs requests from clients to query, retrieve, and print items in the database, which contains object indexes and other information. The library server routes requests to the appropriate object server to store, retrieve, and delete objects.

The library server is part of a Content Manager OnDemand instance. Each Content Manager OnDemand instance:

Has its own folders, application groups, applications, users, groups, storage sets, and printers
Must run in a single code page
Has different security (users, groups, folder and application group permissions)
Must have its name specified on commands if it is not the default instance
Has its own system log

Some reasons to have multiple instances on the same system are:

To have different test and production environments
To have databases that use different code pages

The library server is the central component of the Content Manager OnDemand system. The library server maintains the central database of the objects on the system. The objects are: users, groups, storage sets, storage nodes, printers, application groups, applications, and folders. The library server uses Db2® to manage the database. The standard configuration for the library and object server includes the database and cache storage on one system or node. The library server processes the login requests from the clients, handles the queries from the clients, and maintains the database.