Administering Rational ClearQuest

Learn how to administer the product.

• Basic administration tasksAdministrators are typically responsible for installing the software, creating a release area and installing fix packs. Administrators also create and manage schema repositories and user databases, configuring Lightweight Directory Access Protocol (LDAP) user authentication, managing user accounts, and setting up Rational® ClearQuest® Web.
• Administering Rational ClearQuest WebAdministering Rational ClearQuest Web entails configuring and maintaining services that support the Web client and customizing certain aspects of Web client behavior and appearance.
• Administering Rational ClearQuest MultiSiteMultiSite adds a powerful capability to Rational ClearQuest. With MultiSite, developers at different locations can use the same database set (a schema repository and its associated user databases). Each location has its own copies, or replicas, of the schema repository and user databases. At any time, changes made in one replica can be sent in update packets to other replicas. The update process can be automated or can be started manually with a command.
• Administering Rational ClearQuest

  Administrators are typically responsible for installing the software, creating a release area and installing fix packs. Administrators also create and manage schema repositories and user databases, configuring Lightweight Directory Access Protocol (LDAP) user authentication, managing user accounts, and setting up Rational ClearQuest Web.

• Administering Rational ClearQuest Web

  Administering Rational ClearQuest Web entails configuring and maintaining services that support the Web client and customizing certain aspects of Web client behavior and appearance.

• Administering Rational ClearQuest Multisite

  MultiSite adds a powerful capability to Rational ClearQuest. With MultiSite, developers at different locations can use the same database set (a schema repository and its associated user databases). Each location has its own copies, or replicas, of the schema repository and user databases. At any time, changes made in one replica can be sent in update packets to other replicas. The update process can be automated or can be started manually with a command.