Cc Installation Process


Published on

Published in: Education, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Cc Installation Process

  1. 1. Installing ClearCase This module discusses the tasks involved in ClearCase installation. Refer to the Rational ClearCase Installation Guide for additional details. This module discusses enterprise deployment, which is the standard ClearCase installation option. In the enterprise deployment model, you create a release area on the network that is accessible by all ClearCase hosts. In creating the release area, you select site default parameters. Any number of clients and servers can then be installed from this release area. Step 1: Review Installation Documentation Rational ClearCase Installation Guide Rational ClearCase and ClearCase MultiSite Release Notes Be sure to review all relevant documentation before you begin the installation process. Step 2: Verify Installation Environment Verify system requirements. Prepare your hardware environment. Choose a release host. Select an installation model. Verify System Requirements Check that your system meets all: Hardware requirements Operating system version requirements Operating system patch requirements Since ClearCase is closely tied to the kernel, it is very important that you meet all system requirements, especially those regarding operating system version and patches. The Rational ClearCase and ClearCase MultiSite Release Notes lists specific patches required for each platform, as well as the Web site URLs from which to download the patches. Prepare Your Hardware Environment Select machines for License Server -- holds ClearCase license database files Registry Server -- holds ClearCase registry files VOB Servers -- hold VOB physical storage areas View Servers -- hold view physical storage areas Clients -- execute ClearCase commands Release Host -- holds distribution materials for ClearCase installation
  2. 2. Any server can also be a client. Review the Before You Install section of the Rational ClearCase Installation Guide for details about setting up your hardware environment. Choose a Release Host Release host provides storage for the ClearCase distribution, including executables, config files, and man pages. Must be visible to all ClearCase hosts. Needs fast file-system access. Needs 122–141 MB of disk space, depending on architecture. Should be infrequently booted. Does NOT need to have ClearCase installed. Does NOT have to be backed up. If your Web server is not the same as your release host, the disk space requirement for both hosts is the same. This is because you need to load the release area onto the Web server. See the Planning module for more information regarding Web serverconfiguration. All ClearCase patches should be applied in the release area. Although the release area does not have to be backed up, it is a good idea to back it up so you will not have to re-install patches if the release area is damaged in a crash. Select an Installation Model ClearCase can be installed in a variety of ways to control the amount of disk space consumed on the local machine. Standard — “regular” installation, allowing links to the release area Full-copy — “regular” installation with no links to the release area Mounted — host install using a mounted or pre-populated /usr/atria or ATRIAHOME Link-only — host install using a symbolic link to the release area Deinstall — deinstall software from the local installed host Consider the administrative advantages of each model: The Standard installation model is the best combination of features, reliability, performance, and disk space use. The Full-copy installation model copies all of the software from the release area to the local host. It has no dependence on the network, but it requires a large amount of disk space. The Mounted installation model can simplify the task of maintaining ClearCase on a large number of clients. But there is the potential for all ClearCase clients and servers to fail if the ccase-home-dir becomes inaccessible due to system or network failure. This model is highly dependent upon a stable network. The Link-only installation model provides even greater simplification, but with similar disadvantages. Do not use this model if software from multiple release areas needs to be
  3. 3. installed on a target system. You must reinstall whenever a new version of the software is loaded into the release area from which you install. In choosing an installation model, consider the amount of available storage and the expected patterns of use for the target computer. Is the computer a server or a client or both? Does it need to operate even when the network release area is unavailable? Does it have adequate local disk space for the ClearCase installation and any required VOB or view storage? Is ccase-home-dir on a read-only partition? Step 3: Create Release Area Create a directory that can be mounted or accessed by all ClearCase hosts. Example: /usr/ccase_rls Load distribution materials to this directory. Run the site_prep script on the release host. Type of preparation depends on si e status: t Installing for the first time Upgrading from previous release Creating multiple site defaults per release area To copy distribution files from tape or CD to the release area, run the script. The script will prompt you to choose which platforms to load, then will ask the pathname of your chosen release area. If the directory does not exist, will ask if you would like it to be created. You may copy distribution files for multiple platforms into a single release area. Run site_prep for each platform on the release host. The site_prep Script site_prep [-chmod | -setuid] [-enable_non_root disable_non_root] [-license_host license-host-name] [-registry_host registry-host-name] [-registry_backup registry-backup-host-name] [-registry_region registry-region-name] [-no_query] [-help] The site_prep script modifies some files in the release area and sets up default responses for the installation script. This script must be run as root. -enable_non_root enables non-root users to i stall ClearCase on individual hosts. n -disable_non_root restores the default and allows only root users to install ClearCase. The site_prep script, if run with no options, is an interactive script that performs the following: Makes sure that files in the merged release area are owned by root and write is disabled for all files. db_dumper and db_loader (used by the cleartool reformatvob and reformatview commands) are re-protected to make them setUID root.
  4. 4. Checks to make sure the NIS database will accommodate albd_server with no port number collisions. Prompts you for the names of your license server, registry server, and region, to be used as defaults for the install_release script. Asks if you wish to change the existing host data for setUID operation. These defaults are stored in release-directory/platform/site.dat. For detailed information on site_prep, see the Rational ClearCase Product Family Installation Guide. Executing the site_prep Script Example: # cd /usr/ccase_rls/v5.0/sun5/install # ./site_prep Step 4: Install from Release Area Select order of installation. Install ClearCase on hosts. Complete the installation. Once the release area is set up, you can install on any number of ClearCase clients and servers. Order of Host Installation Install ClearCase on the host that will be the license server, registry server, and credentials server (these can be the same machine). Install ClearCase on the VOB and View servers. Install the clients. Beginning Installation Log on to the host to be installed. Execute the install_release script from the install directory on the release host. The install_release script prompts you for specific installation information. Use <Enter> to accept the defaults established with site_prep. Example: % cd /usr/ccase_rls/v2003/sun5/install % ./install_release
  5. 5. The install_release program handles all ClearCase product family installations on UNIX. This program separates the choice of how the software is installed on the local system (the installation model) from the choice of products being installed. Installation Methods Installations can be on local or remote hosts. When you invoke install_release, you are prompted to select an installation method. Select Local Install if you wish to install ClearCase on the local system (where you are currently logged on). Select Remote Install if you want to install software on a single remote system. Select Multiple Remote Installs if you want to install software (using identical install options) on more than one remote system of the same architecture. You must provide a file containing the host names on which you want to install the software. Select Local Deinstall if you want to remove software from the local system. In case you need to reinstall, be sure to back up VOBs, views, and registry server information, and have an extra copy of your license keys handy. Installation Directory ClearCase executables are placed in the installation directory, /opt/rational/clearcase by default. If a directory other than /opt/rational/clearcase is specified, a link is created from /opt/rational/clearcase to the specified location. You may specify another directory orpress <Enter> to accept the defaults. Release Directory The release directory is the directory into which you load the ClearCase distribution from tape or CD. Pathname to the network-wide release directory (used as target of symbolic links): [/usr/ccase_rls/v5.0/sun5] Use this pathname (not the local path) for all locally installed hosts. Standard and link installations use this location. The pathname in the example is the equivalent of a global pathname. Examples /net/lake/usr/ccase_rls/v5.0/sun5
  6. 6. /hosts/lake/usr/ccase_rls/v5.0/sun5 Complete the Installation A copy of the installation script is stored in the /var/adm/rational/clearcase/log directory. FINAL: servername Errors: 0 Warnings: 0 Log file for this session: /var/adm/rational/clearcase/log/Rational_install.030423.08:36 Remote installation errors/messages are sent as stdout back to the machine where install_release was executed. Reboot, if necessary The text of the log file is the script stdout and stdin as install_release interacted with you for installation parameters. HP requires a reboot. Step 5: Perform Post-Installation Procedures Run cleartool –ver to check the installed version of ClearCase. Run cleartool hostinfo –long to verify the names of your license server and registry server hosts. Run clearlicense to verify that you can access your licenses. Run cleartool lsregion to check your connection to the registry server host. Post-Installation Configuration Options Use cleartool setsite to set various site-wide defaults: view_cache_size view_interop_text_mode view_shareable_dos Use cleartool lssite to list the site-wide defaults. The cleartool setsite command sets or unsets site-wide properties in the ClearCase site config registry. ClearCase uses the value for a site-wide property when you perform an operation that uses that property and you do not specify a value for the property. For example, when you create a view and do not specify one of the shareable DOs options, ClearCase uses the site-wide value. Note: Changing the site-wide property for shareable DOs does not change the property for existing views. To change an existing view’s property, use the chview command. Further reference See the Rational ClearCase Command Reference for more information. ClearCase Installation Demonstration
  7. 7. To view an interactive demonstration of ClearCase installation procedures, go to the ClearCase section of Rational DeveloperWorks: i clearcase/ Installing ClearCase Patches Download patches and service releases from: l/support/upgrades/ patches.html Two ways to patch: Patch network release area (recommended) Installs from the release area will now include the patches Patch individual host Only the individual host will be patched All ClearCase patches and service releases are available at http://www- l/support/upgrades/patches.html Patches for ClearCase are applied to the release areas, and then the application of the patches is performed by executing install_release from the release area again. When patches are downloaded from the Web page, the executable will give the ClearCase Administrator the option of applying the patch changes either to the ClearCase client OR to the network release area. Rational recommends testing the patch on a single system, then patching the release area. Refer to the Rational ClearCase Installation Guide for details. Updating ClearCase: Obtaining Host Information Use the hostinfo command to display information about the local host or a specified remote host. cleartool hostinfo [ -long] [ hostname ...] Example: % cleartool hostinfo hostname: ClearCase 2003.06.00 (SunOS 5.6 Generic sun4u) % cleartool hostinfo -long Client: hostname Product: ClearCase 2003.06.00 Operating system: SunOS 5.8 Generic Hardware type: sun4u Registry host: ruserver
  8. 8. Registry region: unix_region License host: ruserver When upgrading your ClearCase version you must supply host information to install_release if it is different from the defaults. Gather this data before running ./install_release so you can use the information to upgrade your current machine. This command is helpful when trying to troubleshoot problems. Removing a ClearCase Installation To remove a ClearCase installation, run the install script and specify Local Deinstall. The deinstall preserves important system files in /var/tmp/Rational.preserve. Selecting a component for deinstallation causes any other components that depend on that one to be deinstalled at the same time. It is a good idea to deinstall previously installed products before you install the new release. Deinstalling cleans up obsolete links and files from the previous release. Local deinstall preserves the system files rgy, rgy/backup, license.db, and exports.mvfs. vobadm [No View : /] $ cleartool -ver ClearCase version 7.0.1 (Wed May 30 16:54:29 EDT 2007) (Wed Sep 19 16:08:10 EDT 2007) (Wed Dec 05 16:29:24 EST 2007) @(#) MVFS version (Tue Nov 27 23:01:26 2007) cleartool (Wed Nov 7 21:53:18 EST 2007) db_server (Fri Nov 2 11:45:07 EST 2007) VOB database schema version: 54 vobadm [No View: /] $ cleartool hostinfo -long Client: odyssey32 Product: ClearCase Operating system: AIX 1 6 Hardware type: 000C735AD600 Registry host: odyssey32 Registry region: ody_unix License host: odyssey32 vobadm [No View : /] $ clearlicense Licensing information for ClearCase. License server on host quot;odyssey32quot;. Running since Mon Sep 15 16:59:28 2008.
  9. 9. LICENSES: Max-Users Expires Password [status] 5 none 48573966.12e068b0.02 [Valid] 25 none 48573965.f603f0e1.02 [Valid] 20 none 47b27e74.67de8b33.02 [Valid] Maximum active users allowed: 50 Current active users: 3 Available licenses: 47 ACTIVE users: User Priority Time-out in vobadm none 58 minutes (at 15:44:28) omarsae none 53 minutes (at 15:39:43) sshanley none 18 minutes (at 15:04:46) License Usage Statistics: 0 licenses revoked since start ofperiod 10/14/08. 0 license requests denied. 0 active users bumped by preferred user. vobadm [No View : /] $ cleartool lsregion ody_unix ody_win