Object server

Content Manager OnDemand stores and retrieves objects that reside on an object server through requests routed by the library server. An object server is the repository for objects stored on the system. The object server maintains reports that are stored in cache or archive storage. If an object server is configured with archive storage, the object server works with OAM, Tivoli® Storage Manager, or VSAM to manage reports in cache storage and in archive storage. The object server processes data loading operations, document retrieval requests from the clients, and migration and expiration processing.

The object server manages storage resources that are defined through the Content Manager OnDemand administrative programs. A Content Manager OnDemand system can have many object servers distributed across multiple interconnected networks to provide convenient user access. Object servers can run on any supported Content Manager OnDemand environment including AIX®, Solaris, Windows, and z/OS® systems.

Object servers work with the Content Manager OnDemand administrative programs to efficiently manage storage resources. This allows the Content Manager OnDemand administrator to specify the type of archive (HFS, VSAM, OAM, Tivoli Storage Manager), how long documents reside on specific device types before the documents are migrated to another device, and how long Content Manager OnDemand maintains documents on the system before expiring them.

An object server is the component of a Content Manager OnDemand system that holds the reports that are accessed by users. An object server belongs to a Content Manager OnDemand instance. An instance is a logical server environment consisting of a library server, one or more object servers, a database, and cache storage. A Content Manager OnDemand object server:
  • Has its own storage nodes
  • Must run in the same code page as the library server
  • Uses the security from the library server
Some reasons to have more than one object server are:
  • To distribute the storage of data across multiple systems or locations
  • To be able to load data into more than one storage node at a time