Home
Developing
Learn how to develop software with DevOps Code ClearCase® and ClearCase Remote Client.
Developing software with ClearTeam® Explorer
DevOps Code ClearCase® provides two clients for software developers: local and remote. Each client supports different mechanisms for accessing source-controlled filesystem objects. Both clients provide graphical and command-line interfaces.
Team software development with ClearCase®
DevOps Code ClearCase® provides configuration management services that make it easy for development teams to work with resources in a shared repository. With the ClearTeam® Explorer, developers can access DevOps Code ClearCase from a variety of network connections, including broadband (WAN) and traditional local area networks (LANs). The ClearTeam Explorer also supports WAN access to Rational® ClearQuest® user databases.
About ACL authorization
If access control list (ACL) authorization is enabled, the identities and protection modes for some object types are administered through policies, which define permissions for roles; and rolemaps, which map the roles to principals.
Element protection
The ability to protect directory and file elements with ACLs greatly simplifies authorization administration. The simplification uses multiple groups in element effective ACLs in place of multiple groups in each user's credentials.
Access control lists and principals
With ACLs enabled in a VOB, the access checks performed in ClearCase® compare a process's credentials against an effective ACL associated with an object (VOB object, element, policy, or rolemap).

Access control lists and principals

With ACLs enabled in a VOB, the access checks performed in ClearCase® compare a process's credentials against an effective ACL associated with an object (VOB object, element, policy, or rolemap).

The generated effective ACL (derived from a rolemap and its implemented policy) will list users, groups, or one of the special principal kinds. The groups used in ACLs are not limited to the VOB's groups. The groups and users listed in a policy or rolemap can be any group that is known both to the VOB server's operating system and to the file system storing the VOB's elements. For example, when using NFSv4 filer storage, the VOB server and the filer both need to be able to identify the user name or group name.