|
|
ClearCase supports these NFS client products on Windows NT computers:
Microsoft Windows NT Services for UNIX Client for NFS Products (SFU 1.0)
Intergraph DiskAccess
Hummingbird NFS Maestro
If you are using an NFS client product, you must install it on each Windows NT client that will access VOBs or views located on UNIX servers. You must install the product correctly and completely; in particular, you must assign and configure the NFS daemon and authentication process.
NOTE: The READ ME FIRST chapter in ClearCase and MultiSite Release Notes (Windows edition) contains last-minute information about NFS client products, including which versions of those products ClearCase supports.For more information about configuring NFS client products, read the remainder of that manual.
The rest of this section describes configuration procedures specific to using an NFS client product with ClearCase. Read and perform all procedures recommended for your product.
Some NFS client products change the case of file names by default, typically by converting to lowercase. Because ClearCase is case-sensitive, you need to disable case conversion, as described later in this section.
NOTE: Typically, you can use a command-line option to disable case conversion for a particular NFS mount. However, ClearCase can automount remote storage directories. See Automounting and NFS Client Software. For correct behavior on these mounts, configure NFS mount drive options to disable case conversion.
To disable automatic case conversion:
Start the Client for NFS (for SFU) or DiskAccess (for DiskAccess) Control Panel program.
On the Filenames tab, click Preserve Case (no conversion).
To disable automatic case conversion:
Click Start >Settings >Control Panel. Start the Network program.
On the Services tab, select NFS Maestro for Windows NT Client.
Click Properties to open the client configuration dialog box.
Under Filename Capitalization, click Preserve Case.
If you plan to work in a shared UNIX view, configure your NFS client with a default protection that grants group write access. Without this permission, other developers cannot modify view-private files that you have created.
To set the default protection:
Start the Client for NFS (for SFU) or DiskAccess (for DiskAccess) Control Panel program.
On the File Access tab, ensure User is RWX, Group is RWX, and Other is RX.
To set the default protection:
Click Start >Settings >Control Panel. Start the Network program.
On the Services tab, select NFS Maestro for Windows NT -Client.
Click Properties to open the client configuration dialog box.
Under Default Protection, specify the protections as follows:
User Group Other
RWX RWX RWX
xxx xxx x x
To avoid VOB and view access permission problems, do not log on to an NFS server as user nobody or with any user or group ID that does not match your Windows NT user and primary group IDs.
To verify that your Windows NT user name/UID and group name/GID match their UNIX counterparts, pass the name of a UNIX NFS server to ccase-home-dir\etc\utils\credmap. For example:
ccase-home-dir\etc\utils\credmap saturn
After you confirm your user name/UID and group name/GID, supply the user name as an NFS logon parameter.
Start the Client for NFS (for SFU) or DiskAccess (for DiskAccess) Control Panel program.
On the Authentication tab, type the correct User Name, Password, and PCNFSD Server.
Click OK; your logon session is validated.
To set your logon user name; at the command prompt, run the nfs register command:
nfs register username
This command prompts for a password.
The Maestro DOS Sharing option is incompatible with ClearCase use. When using Hummingbird NFS Maestro with ClearCase, you must disable this mode. If you do not, you may encounter MVFS log errors when attempting to open MVFS files. For example:
ZwOpenFile returned status 0xc0000043
This error indicates a sharing violation.
Start the Network program in Control Panel.
On the Services tab, select NFS Maestro for Windows NT -Client.
Click Properties to open the client configuration dialog box.
Under Default Links, clear the DOS-Style Sharing check box.
When you mount a UNIX VOB or start a UNIX dynamic view, ClearCase needs to access the VOB storage directory or view storage directory on the UNIX file-system partition. In the ClearCase program in Control Panel, the setting of the Enable automatic mounting of NFS storage directories check box determines how ClearCase accesses those directories when you use NFS client products.
All supported NFS client products can process UNC names. If you are using one of these products, clear the Enable automatic mounting of NFS storage directories check box. ClearCase then uses UNC names to access UNIX VOB and view storage directories. We recommend that you configure ClearCase hosts in this way.
If you have been using ClearCase with the Enable automatic mounting of NFS storage directories check box selected, you can continue to do so. ClearCase then maps Windows drive letters to UNIX VOB and view storage directories and accesses the directories through those drive letters.
NOTE: These drive letters are for internal ClearCase use. They are different from the drive letters you can assign and use for your own work within views. In particular, do not confuse them with the drive letters you can assign to dynamic views when you start those views.
We recommend that you disable automounting when using any supported NFS client product. If you install Microsoft SFU or Intergraph DiskAccess before you install ClearCase, the ClearCase installation procedure disables automounting for you.
If you are using Hummingbird NFS Maestro or if you install a supported NFS product after you have installed ClearCase, you can disable automounting using the ClearCase program in Control Panel.
Click Start >Settings >Control Panel. Open the ClearCase program.
On the Options tab, clear the Enable automatic mounting of NFS storage directories check box.
Click OK.
SFU and DiskAccess use a scheme to map Windows NT user credentials to NFS user and group ID. This scheme requires that you perform an additional setup procedure for the special ClearCase server process user account, as described in Administering ClearCase.
The setup procedure enables ClearCase services to access remote NFS view and VOB storage directories with the proper privileges, which enables operations such as cleartext construction.
Cleartext construction is the process by which data is extracted from the VOB storage area source container by a ClearCase type manager. This type manager then constructs or creates a cleartext container the first time a version is accessed. For faster access, subsequent reads of that version access the cleartext file directly.
On UNIX, the group ID (GID) is used for the permission to construct cleartext. The UNIX primary group name must match the user's Windows NT primary group name.
NOTE: By convention, the name of the ClearCase group is clearcase. A community can choose a different name as long as all ClearCase hosts in the community define the ClearCase group as that group name. If multiple communities share a single Windows NT domain, each community must have a unique name for its ClearCase group.
As part of setting up SFU or DiskAccess, the administrator needs to supply the ClearCase server process user with a valid UNIX name and password for a user account that belongs to the correct primary group. The administrator can identify the UNIX account by performing one of the following tasks:
Add a UNIX account that matches the Windows NT name of the ClearCase server process user account.
Add a new UNIX account that does not match the Windows NT name.
Use an existing UNIX account.
Set up the ClearCase server process user account (clearcase_albd) on every ClearCase Windows NT client that will access remote NFS views or VOBS. For the first client, follow the steps below. For subsequent clients, either follow the steps here or perform the steps in Alternative Setup: Administrative Option.
Install SFU or DiskAccess, restart, and set up your regular user account, from which you will log on to SFU or DiskAccess.
Log off from your current user session.
Log on as the ClearCase server process user on your system.
Start the Client for NFS (for SFU) or DiskAccess (for DiskAccess) Control Panel program.
On the Authentication tab, specify the UNIX name and password that you established in Setting Up the UNIX Account.
Click OK.
When you exit the Client for NFS (for SFU) or DiskAccess (for DiskAccess) program, read the confirmation dialog box. Verify that you are currently logged on with the desired UID and GID.
If there is an error, or if you are logged on with UID and GID of -1 and -2, repeat Step #3 through Step #6 in this section.
Log off.
Instead of performing the steps in Preparing the Windows NT Client, you can instead perform the steps in this section. For example, it may be inconvenient to log on as the ClearCase server process user on every client system. As an alternative, perform the following steps:
Log on as the ClearCase server process user (clearcase_albd) on one system.
Run the Windows Registry Editor (type regedit in the Run dialog box or from a command prompt).
Carefully save the security-id key here:
HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph\DiskAccess\CurrentVersion\Users
Select the security-id subkey whose Name key value is your ClearCase server process user account name. To find the correct subkey, type the following command, and look on the line in the output that starts with SID:
ccase-home-dir\etc\utils\creds clearcase_albd
NOTE: If your community uses a ClearCase server process user account name other than clearcase_albd, use that name instead.
Save the key to a registry file by clicking Registry >Export Registry File in the Registry Editor.
To share the registry file, mail it to users or place it on a shared directory. When users want to load the file into the registry, they double-click the file name in a file browser such as Windows Explorer. The system displays a confirmation message after it loads the file.
All users who use the same ClearCase server process user account and the same primary Windows NT group that maps to the UNIX GID to which it was logged on can share this file.
Browsing of UNIX resources from Windows NT is not enabled by default on SFU. You must enable this feature manually for it to work. Otherwise, users cannot browse for UNIX resources using either net view at the command prompt or Network Neighborhood on the desktop. After configuring the client for NFS, take the following steps:
Start the Client for NFS Control Panel program.
On the Configured NFS LANs tab, click Add, enter a name for the LAN (for example, Default_LAN), click Specify LAN to browse, and then click OK.
On the Configured NFS LANs tab, click Edit, and in the Broadcast Address box type 255.255.255.255. You can either accept the defaults or customize the rest of the broadcast parameters.
Click OK in the Broadcasting dialog box; then click OK in the Client for NFS dialog box.
NOTE: Configuring SFU for browsing as described here is not required by ClearCase and increases the UDP broadcast traffic on your network.
|
|
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |
