albd_server process

When a client program needs access to a service (a VOB or view server, for example) on a Rational® ClearCase® server host, it uses a remote procedure call (RPC) to send a request to the albd_server process on that host. The albd_server starts the requested service if it is not already started, and provides the service's port number to the client. Thereafter, the client communicates directly with the service.

The albd_server handles a variety of tasks on hosts configured to support local VOBs and views:

Starting and stopping other Rational ClearCase services as needed.
Setting up network communications between Rational ClearCase clients and servers.
Managing execution of tasks run by the Rational ClearCase scheduler.
Responding to requests for registry information on a Rational ClearCase registry server host.
Responding to requests for licenses on a Rational ClearCase license server host.
On hosts running Linux® or the UNIX® system, responding to load-balancing queries from a remote clearmake process.

When you start Rational ClearCase, the albd_server starts first and runs with one of the following user identities:

As root on Linux or on the UNIX system
A specially created privileged user account on Rational ClearCase on Windows®

When you stop Rational ClearCase, the albd_server stops all Rational ClearCase services on the host and then exits.

Rational ClearCase services started by the albd_server generally run with the identity of the resource (VOB or view) owner on Linux or the UNIX system, and with the identity of the albd_server on Windows.

Port assignment

The albd_server process listens for RPCs on a well-known port (port 371) that has been reserved for it by the Internet Assigned Numbers Authority. Rational ClearCase installation verifies that no other service uses this port for UDP or TCP communications. If a conflict is detected, you must assign another port to the conflicting service. If you cannot reconfigure or remove the conflicting service, you must configure thealbd_server to use a different UDP port.

On Linux or the UNIX system, edit the local host's services database or the NIS services map.
On Windows, create the appropriate entry in the file %SystemRoot%\System32\drivers\etc\services. (If there is no entry for the albd_server in this file, it uses port 371.)

Note: All albd_server processes in a community must use the same port number. If you change the albd_server port assignment on any Rational ClearCase host, you must change it on every Rational ClearCase host.

The albd_server reads configuration file albd.conf during startup to determine which services to provide. Do not modify this file.