Instances

A Content Manager OnDemand instance is a logical server environment made up of a database, a library server, and one or more object servers. An instance is defined in the ars.ini file by naming the instance, identifying the name of the database used by the instance, and identifying the library server on which the database will be maintained. When you configure an object server, you identify its library server in the ars.cfg file on the object server. An instance has its own cache storage file systems. The cache storage file systems are defined in the ars.cache file on each object server. All of the servers that belong to an instance run in one and only one code page.

You can run multiple instances on the same system, with each instance configured differently:

To have separate test and production environments
To have databases using different code pages

Important: When you work with more than one instance, you must identify the instance name when you run Content Manager OnDemand programs (such as ARSDB, ARSLOAD, and ARSSOCKD) and database commands (such as connecting to the database).

Each instance has different security from other instances on the same machine. You must define users and groups to each instance and set application group and folder permissions for users of each instance. Each instance has its own system log.

Each additional instance requires additional system resources, such as virtual storage and disk space, and more administration. For example, you must make sure that the ars.ini file is consistent and correct on all servers that are part of a logical Content Manager OnDemand system.