In mixed networks of Windows and UNIX computers, certain ClearCase operations may require a Windows or UNIX computer to access the file system of a different type of computer. Rational ClearCase supports several protocols that allow a Windows computer to access the file system of a UNIX computer and also provides for more limited access by UNIX computers to ClearCase data in Windows file systems. The following protocols-some of which can only be enabled using a software from a third party (neither Rational nor the computer vendor)-may be used.
ClearCase File Service (CCFS) - The ClearCase File Service is a TCP/IP-based file transfer mechanism included with ClearCase. It provides snapshot views with access to VOB data. It does not support dynamic views. For information about CCFS, see ClearCase File Service.
NFS - The NFS (Network File Service) protocol is supported by most UNIX computers for network file system access. NFS client products for Windows allow Windows computers to access UNIX file systems using the NFS protocol. You install an NFS client product on each Windows computer from which you want to access UNIX VOBs and views. For more information about which NFS client products ClearCase supports and how to configure them, see NFS Client Products.
SMB - The SMB (Server Message Block) protocol is the native protocol that Windows computers use for network file system access. SMB servers that run on UNIX computers allow Windows computers to access UNIX VOBs and views using native Windows protocols. You install an SMB server product on each UNIX VOB or view server you will access from a Windows client. For more information about which SMB server products ClearCase supports and how to configure them, see SMB Server Products
Table 4 lists the protocols that ClearCase clients can use to access VOB data. Table 5 lists the protocols that ClearCase clients use to access view_server storage. In these tables, protocols native to their respective computer platforms are labeled "Native."CCFS is included in ClearCase. All other protocols require third-party software support.
Client Platform | Access to VOB data on UNIX | Access to VOB data on Windows |
---|---|---|
Windows 98, Windows Me | CCFS (requires Windows view server) | Native SMB |
Windows (dynamic views) | Third-party NFS or SMB | Native SMB |
Windows (snapshot views) | CCFS, third-party NFS or SMB | Native SMB |
UNIX (dynamic views) | Native NFS | Unsupported |
UNIX (snapshot views) | Native NFS | CCFS |
Client Platform | Access to view data on UNIX | Access to view data on Windows |
---|---|---|
Windows 98, Windows Me | See note. | Native SMB |
Windows (dynamic views) | Third-party NFS or SMB | Native SMB |
Windows (snapshot views) | Third-party NFS or SMB | Native SMB |
UNIX (dynamic views) | Native NFS | Unsupported |
UNIX (snapshot views) | Native NFS | See note. |
NOTE: When a view has been created with the -ngpath option and both the client and server platforms are running ClearCase 4.1 or later, Windows 98 and Windows Me platforms can access view data on UNIX, and UNIX snapshot views can access view data on Windows using the native ClearCase RPC mechanism. This configuration is found most often in ClearCase LT communities.
Table 6 lists the protocols used by a view_server process to access VOB data.
view_server platform | Access to VOB data on UNIX | Access to VOB data on Windows |
---|---|---|
Windows | CCFS, third-party NFS, or SMB | Native SMB |
UNIX | Native NFS | CCFS |
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |