|
|
This section describes the following platform-related issues of a general nature:
Rational ClearCase is implemented using a set of shared libraries. In addition, Rational Software supplies three shared libraries from vendors in ccase-home-dir/shlib (where ccase-home-dir is your installation directory, /usr/atria by default). The libraries are the C++ compiler library libC.so or libC.sl (depending on vendor; other possible shared C compiler library names follow the pattern libCstring.so, where string may be any short character string), the Galaxy run-time library libvgalaxy++.so (or libvgalaxy++.sl, depending on vendor), and the EZ-RPC runtime library libezrpc.so (.sl).
If you install in the default install location, or if you install in a nondefault location but use a symbolic link from ccase-home-dir to your install directory, the executables are capable of locating all shared libraries correctly.
If, for any reason, the ClearCase libraries in the ccase-home-dir/shlib directory are missing, the ClearCase executables do not run.
If you install Rational ClearCase in a nondefault location, that is, other than /usr/atria, you must set the proper platform-dependent library search-path environment variable to include the ccase-home-dir/shlib pathname so that ClearCase executables can find the required ClearCase shared libraries and vendor-supplied libraries.
The order of the pathnames in the environment variable is important. At run time, ClearCase must find the three vendor libraries supplied by Rational Software before it finds any other versions of those libraries in other paths in the list. Other applications that use this definition of the library search-path environment variable may find these supplied vendor libraries instead of other versions of those libraries installed on your system. This behavior may or may not be compatible with those applications.
If the supplied vendor libraries are missing, the executables may search the system libraries (the order of search, where it searches, and whether it searches is platform dependent). If a library of the appropriate name is found, the execution may not succeed because the library found may not be compatible with the ClearCase executable.
The following table indicates the search-path environment variable that you need to define on each supported UNIX platform so that you can access the ClearCase shared libraries. To find the architecture mnemonic associated with your platform, see the sections dealing with individual platforms.
| Architecture Mnemonic | Search-Path Environment-Variable Names |
|---|---|
sun5 | LD_LIBRARY_PATH |
| |
hp10_pa, hp11_pa | SHLIB_PATH |
When running clearmake, you can invoke compatibility modes to incorporate features of make programs native to some UNIX platforms. For details, see the chapter Using clearmake Compatibility Modes in Building Software.
Some platforms continue to provide Cfront-based compilers. If you are using such a compiler, you may find detailed information about the best way to use it with ClearCase in the chapter Using ClearCase to Build C++ Programs in Building Software. In general, we recommend that you use a compiler that supports the ANSI C++ explicit instantiation syntax for best results with ClearCase.
ClearCase is a client/server application. Developers use client hosts to run the client programs that constitute the user-level interface to ClearCase. ClearCase data (for example, VOB storage directories and view storage directories) reside on server hosts. ClearCase server processes execute on server hosts as needed, communicating with client programs through remote procedure calls (RPCs).
In general, the ability of a UNIX computer to act as a ClearCase server depends more on its ClearCase installation model (Standard, Full Copy, Mounted, or Link) than on its platform.
For descriptions of the installation models and of the requirements for ClearCase server hosts and client hosts, see the Installation Guide.
All UNIX platforms that ClearCase supports can act as registry, license, or view servers. A typical developer's workstation is both a client host (because the developer runs CPF product programs on it) and a server host (because the developer's views reside there, too).
All UNIX platforms that ClearCase supports can also act as VOB servers. However, the ability to act as a VOB server in a heterogeneous environment may have some platform dependencies. To ensure that any computer on which you are planning to host a VOB can act as a VOB server to all its intended clients, see the sections on individual platforms.
For details on using UNIX systems as ClearCase servers in a Windows/UNIX environment, see the Administrator's Guide.
The following reference pages include information specific to UNIX platforms:
WARNING: On some UNIX systems (for example, HP and Solaris), tar sets file access times to the current time when it is run, which can interfere with derived object (DO) and cleartext storage pool scrubbing patterns. For example, a nightly tar operation backs up DO pools. The scrubber utility, by default, scrubs only DOs not accessed in four days (96 hours). Because DOs from the backed-up pools never appear to be more than one day old, they are never scrubbed. For more information on backup procedures, see the chapters on administering VOBs and views in the Administrator's Guide.
|
|
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |
