ClearCase is compatible with a wide variety of domain configurations. The simplest configuration-a single domain that includes all users, groups, and computers-entails the least administrative overhead, but other common configurations work equally well:
Master and multi-master Windows NT domain configurations in which user and group accounts are created in a master domain and host (computer) accounts are created in one or more resource domains that trust the master domain.
Active Directory domains that are part of a single forest.
Domain upgrade and domain migration environments that support a combination of Windows NT and Active Directory domains.
ClearCase imposes a few simple requirements on any domain environment in which it operates:
All members of a ClearCase community (all users who access the same VOBs and views) must have domain accounts and have at least one group membership in common.
All ClearCase hosts must be members of a domain. If the hosts are not members of the same domain in which the user and group accounts are created, they must be members of a domain that trusts that domain.
If members of the ClearCase community access VOBs and views on UNIX hosts, user and group names for their domain accounts must be identical to those in UNIX account database. (Some cross-platform file access solutions require the passwords to be the same as well.)
A special domain account must be created to provide a user identity for the albd_server process.
Additional steps must be taken to enable users from multiple domains to access a common set of VOBs and views.
Windows computers that are not in a domain can be ClearCase hosts, though with severely limited functionality:
They cannot host ClearCase VOBs or views used by other ClearCase hosts.
They cannot access VOBs and views hosted on other Windows computers.
Nondomain systems can function as ClearCase clients in networks in which all VOB and view storage resides on UNIX hosts.
Nondomain systems can also function as stand-alone systems on which all VOBs and views are used locally. This situation typically arises when you are evaluating ClearCase software. For more information, see Installation Guide for the ClearCase Product Family.
For information about administering nondomain systems, see Chapter 5, Configuring ClearCase in a Mixed Network.
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |