Database servers

When you configure the library server, you determine the number of processes that Content Manager OnDemand can start on the library server to support database requests. This provides a performance advantage by distributing the server workload over several processes, while balancing the impact on system resources.

In addition to database connections by Content Manager OnDemand client programs, the value that you specify must support the number of active Content Manager OnDemand commands and services such as ARSLOAD, ARSDOC, ARSODF, ARSMAINT, and ARSADMIN.

Each connection to the Content Manager OnDemand database requires a database agent. Content Manager OnDemand can start a database agent for each connection. However, each agent requires its own private memory and some portion of application shared memory. You configure the Number of Database Servers parameter to optimize the way that Content Manager OnDemand handles the database load. For example, you can configure the server so that Content Manager OnDemand starts a fixed number of database agents, regardless of the number of concurrent database requests. While this might appear restrictive, database requests typically process very quickly. For example, ten database agents can handle many database requests, while balancing the impact on system resources.

You should set the Number of Database Servers parameter to support the peak number of concurrent database connections that you expect the library server to handle. A low value limits access to the database during periods of high database activity. A high value requires more system resources during periods of high database activity. The value that you choose also depends on the characteristics of the queries. For example, general queries typically keep a connection open longer than a more specific query.