Managing Content Servers

The default Content Server installation creates a repository with one server. In Documentum Administrator, administrators can configure additional servers to run against a particular repository.

Each Content Server is associated with a server configuration object. A server configuration object is a template for a Content Server. A server configuration is defined by the properties in the associated server configuration object and the parameters in the server.ini file that is read during server startup. At startup, a server always reads the CURRENT version of its server configuration object.

All server configuration objects for the current repository are listed on the Content Server Configuration page in Documentum Administrator, as described in Table 2.6.

Server configuration objects are stored in the repository System cabinet. You can add Content Servers by creating multiple server configuration objects, as long as they are uniquely named. You can also modify a server configuration object and save it as a new object.

Note

For information about creating, starting, and stopping a remote Content Server, refer to the Content Server Installation Guide and Distributed Configuration Guide.

Table 2.6. Server configuration object information

ColumnDescription

Name

The name of the server configuration object.

Host

The name of the host on which the Content Server associated with the server configuration object is running.

Operational Status

The current running status and dormancy status separated by a comma of the Content Server. Valid values are:

Running Status:

  • Running

  • Unknown

Dormancy Status:

  • Dormancy Requested

  • Dormant

  • Active

  • Invalid

Note

The Operational Status column will display only the current running status for Content Server versions prior to 7.0.

Version

The version of the server configuration object.