Server Configuration File

When it starts, the AccuRev Server program reads configuration file acserver.cnf, located in the AccuRev executables directory. This configuration file is generated during installation, but can be edited manually thereafter.

Important! After editing this file, you must restart the AccuRev server. If you have edited the values for SITE_SLICE_LOC, MASTER_SERVER, or PORT, you must also run the maintain server_properties update command before the new values will take effect. See ‘The ‘maintain’ Utility for more information.

Here are some sample acserver.cnf settings:

MASTER_SERVER = accurev_server_machine.company.com
PORT = 5050
SITE_SLICE_LOC = /partition0/site_slice
DEPOTS_DEFAULT = C:\Program Files\AccuRev\storage\depots

Important! The white space surrounding the equals sign (=) in configuration files is mandatory.

The MASTER_SERVER name should be the fully-qualified name of the server machine, including a domain name and Internet extension. Using just the server name may work in most situations, but fully-qualified is preferred. Alternatively, you can use the IP address of the server machine.

The PORT setting contains the port that the AccuRev Server is available on.

The SITE_SLICE_LOC setting points to the directory that the Server uses for storing repository-wide AccuWork data, workflow configuration data, server preferences, and triggers. This directory:

•	Must be owned by the operating-system account that the Server runs as (for example, acserver).

•	Must be physically located on the server machine. The SITE_SLICE_LOC location must not be within a remotely mounted file system (UNIX/Linux) or within a shared directory (Windows) on a remote machine.

The DEPOTS_DEFAULT setting points to the directory that the Server uses for new depots, for storing the files created when a permanent copy of a version is created with the keep command. Note that if you move an existing depot, this variable is not used — you must tell AccuRev about the new location with chslice.

UNIX/Linux: Controlling the Server’s Operating-System User Identity

The following specifications determine the user identity and group membership of the operating system process in which the AccuRev Server runs:

USER = <user-name>
GROUP = <group-name>

When the AccuRev Server is started automatically (usually at system boot), it changes its user identity and group membership according to the USER and GROUP settings in the acserver.cnf file. (See Controlling Server Operation.)

With these settings commented out, the AccuRev Server runs under the identity of the user who started it.

UNIX/Linux: Setting the Server’s Home Directory

In addition to having a user identity and group membership, the AccuRev Server has an AccuRev home directory. This directory is used for a variety of purposes — for example, to store a login session file created by a server_admin_trig trigger script.

By default, the AccuRev home directory is the same as the operating-system home directory, as indicated by the environment variable HOME. It’s a best practice to override the HOME value by setting the value of environment variable ACCUREV_HOME. If the AccuRev Server is started automatically at system startup time by a script in the “rc” or “init.d” directory, the most logical place to set the AccuRev home directory is in this startup script:

export ACCUREV_HOME=/users/acserver

Controlling Login Session Longevity

A successful user login creates a session that by default expires 4 hours (240 minutes) after the last AccuRev command is executed. You can change this behavior by creating or modifying this acserver.cnf setting:

SESSION_TIMEOUT = <number-of-minutes>

On UNIX/Linux systems, a user can control the timeout for an individual session by setting environment variable SESSION_TIMEOUT before logging in. For example, to set a 15-minute timeout interval for a single session:

export SESSION_TIMEOUT=15
accurev login derek

Non-expiring login sessions

The following setting in acserver.cnf causes user sessions never to expire:

SESSION_TIMEOUT = 0

No matter what the setting, users can create non-expiring sessions with login –n.

Controlling Multithreading of the AccuRev Server

The AccuRev Server is a multi-threaded program, architected to support a maximum of 256 concurrent threads. To conserve system resources, you can specify a lower maximum in the acserver.cnf file:

MAX_THREADS = 25

As it’s running, the AccuRev Server may reduce the maximum even further than the specified MAX_THREADS level, depending on the available computing resources.

Configuring Access to the Database

The AccuRev Server (as of Version 5.0) uses the third-party database PostgreSQL. The settings listed below are configured at installation.

DB_DRIVER = Postgres
DB_CONNECT = localhost:5075@accurev
DB_USER = acserver
DB_PASS = e8c5ed8f07bfaf44d2f2eebc215e3cf3
DB_HOME = <ac_install>\postgresql\9.5

•	DB_DRIVER – Identifies the third-party database used by AccuRev. This setting should not be changed.

•	DB_CONNECT – Identifies the database server, port, and name used by AccuRev. This setting should only be changed if you change the port that the AccuRev database server uses.

•	DB_USER – Identifies the database user AccuRev uses to connect to the third-party database. This setting can be changed using the maintain setcnf command.

•	DB_PASS – Identifies the (encrypted) password for DB_USER. This setting can be changed using the maintain setcnf command.

•	DB_HOME – Identifies the location of the binaries and libraries used by the third-party database. This setting is used by the accurev backup command, and should not be changed.