Deployment Planning for IBM Rational ClearQuest Version 7.1

To get optimal use from the new features in IBM Rational® ClearQuest® 7.1, some customization and configuration is required. This article gives an overview of the new features and necessary configuration tasks.

Shireen Ahmed (shireen@us.ibm.com ), Senior Staff Software Engineer, IBM

Shireen Ahmed photoShireen Ahmed has been with IBM Rational since 2002. She has led and worked on several projects focusing on IBM Rational ClearQuest and globalization (G11N), and she co-authored an IBM Redbook titled "Certification Study Guide Series: IBM Maximo Asset Management V7.1." Ms. Ahmed previously spent more than 20 years as a software developer in Eastman Software, Viewlogic, and Wang Laboratories. She holds a master’s degree in computer science from Boston University and a master's degree in mathematics from Northeastern University.



17 September 2009

Also available in Chinese

Version 7.1 adds many features to IBM® Rational® ClearQuest®. As in past releases, some of these new features require configuration by an administrator before they can be used. This article provides an overview of all necessary configuration tasks and refers to the product documentation for detailed information for your deployment.

New features in ClearQuest 7.1

When planning your deployment, it is important to determine which features will be used in your deployment. These new features must be configured:

  • IBM® Installation Manager: A single installation technology used by most IBM Rational applications
  • Rational ClearQuest Web Server
  • Change Management (CM) Server: A unified application server for both ClearQuest Web and IBM® Rational® ClearCase® Remote Client.
  • Logging for monitoring and debugging
  • Enhanced, flexible, multisource data-pull reporting with the Business Intelligence Reporting Tool (BIRT) or Crystal Reports
  • Disable or re-enable Remember Password
  • Support for multiple LDAP configurations
  • Spell-checking in the Eclipse client for Rational ClearQuest
  • Result set limitations for the maximum number of rows returned that can be configured
  • Feature Level 7 is the default when you create a schema repository with the Maintenance Tool. These additional capabilities are enabled with Feature Level 7:
    • Pessimistic record locking
    • Full-Text Search
    • FIPS (Federal Information Processing Standards) 140-2 encryption
  • Full-Text Search capability, which provides natural language queries in ClearQuest Web
  • Pessimistic record locking, which provides a way to prevent situations where multiple users can edit a record at the same time
  • Use of FIPS (Federal Information Processing Standards) 140-2 encryption certified algorithms
  • Application Lifecycle Management (ALM) packages and ALM schemas that are integrated with IBM Rational ClearCase UCM (Unified Change Management) and IBM® Rational® Build Forge®

Features that require minimal configuration

  • The new Rational ClearQuest Web client, which is a browser-based interface to Rational ClearQuest that runs on Microsoft® Windows®, as well as the UNIX® and Linux® operating systems
  • An Eclipse-based Rational ClearQuest Designer, with new features to reduce the time that you need to spend on schema design
  • A rewritten import tool that provides multiplatform support (Windows, Linux, UNIX)
  • New cqtool command line interface (CLI) with multiplatform support
  • Change management API, a new Java™-based API specification for interacting programmatically with Rational ClearQuest and Rational ClearCase (This API for Rational ClearQuest currently requires a local ClearQuest core for LAN access)
  • IPv6 support for customers who must comply with U.S. Federal Government standards

What's new in IBM Rational ClearQuest Version 7.1 , an IBM developerWorks article by Michael Manning (November 2008), provides a quick summary of these features.

The ClearQuest 7.1 client feature comparison matrix provides a feature comparison matrix between the between the ClearQuest Web client, the native client for Microsoft Windows, as well as the Eclipse-based clients.

Table 1 shows the deployment considerations by category.

Table 1. Overview of the ClearQuest deployment considerations
PlanBack upInstallRestore dataTest, go liveConfigure
Topology Hardware SoftwareFirst time:
  1. Install IM
  2. Install ClearQuest
If necessary:
  1. Data
  2. Config. info
  3. Customization
  1. ClearQuest Web
  2. Other clients and servers
  1. ClearQuest Web server
  2. CM Server
  3. Reporting
  4. Full-Text Search
  5. Feature Level 7
  6. FIPS 140-2
  7. Pessimistic Record Lock
  8. Multiple LDAP configurations
  9. Logging
  10. Result set limit
  11. Remember Password
  12. Spellcheck
  13. ClearQuest EC
If upgrade
  1. Data
  2. Config. info
  3. Customization
  1. Uninstall
  2. Install IM
  3. Install ClearQuest

Planning

Administrators of Rational ClearQuest environments are typically responsible for planning the deployment and environment in addition to performing any preinstallation configuration tasks. Thorough planning needs to take place for all components before a rollout. The more up-front planning that you do, the simpler the tasks become during and after an installation. It is not only the software components that need to be thought out; the hardware requirements need an equal amount of thorough planning.

The Planning your deployment section of the ClearQuest 7.1 Information Center covers the general deployment considerations and tasks.

Topology planning

There are certain common physical and logical deployment considerations that administrators must take into account before installation of the product. The following information should be helpful in defining a topology for your deployment.

General suggestions for disk space, RAM, and virtual machines

For every instance of IBM® WebSphere® Application Server:
2 GB RAM dedicated per Java™ Virtual Machine (JVM) instance

Note:
The maximum is 2 GB on 32-bit architectures per JVM instance. A 64-bit architecture with a 64-bit JVM can have much higher amounts of RAM.

Rational ClearQuest 7.1 or later minimum recommended hardware:

  • Server: 2-4 CPUs, 4-8 GB RAM, 80 GB hard disk space, wired connectivity 100 MB full duplex or higher (wireless connection is not suitable for a server)
  • Client: 1.5 Hz 32-bit (x86) or 64-bit (x64) processor or higher, 1 GB RAM (2 GB recommended for development machines), 40 GB hard disk space, wireless 802.11 g (54 mbps or higher), wired connectivity 100 MB full duplex (recommended)

Also see the table for minimum recommended hardware for updates to Rational ClearQuest 7.1 or later.

The use of virtual machines can be cost-effective. If you are considering Virtual Machines in your deployment, see the answer to Are IBM Rational ClearCase, ClearQuest and RequisitePro supported on VMware? from IBM Support.

Server configuration options

Table 2 identifies the different server applications that can be configured on the same host (✔ = supported).

Table 2. Server applications and hosts
ClearQuest Web and CM ServersReport server for ClearQuestFull-Text Search serverLicense server
ClearQuest Web and CM ServerClearQuest Web and CM Server must be installed on the same host.
Report Server for BIRT or Crystal Reports data-pull reports and report server for Crystal Reports (data-pull and push reports)

Report servers can be installed on the same host as ClearQuest Web and CM Server, especially if reporting is lightly used and the report server is supported on that platform. Example: If your ClearQuest Web or CM Server is on Solaris, then you cannot install either report server.


ClearQuest Web client is independent from the license server; therefore, it does not need to be on the same host. Optimal connectivity to the license server is desirable; otherwise, there might be delays in checking out licenses.
Report server for ClearQuest (for BIRT or Crystal Reports data-pull reports) and Report Server for Crystal Reports (Data Pull and Push Reports)
Report servers can be installed on the same host as ClearQuest Web and CM Server, especially if reporting is lightly used and the report server is supported on that platform.
Example: If your ClearQuest Web or CM Server is on Solaris, then you cannot install either report server.


ClearQuest Web client is independent of the license server; therefore, it does not need to be on the same host. Optimal connectivity to the license server is desirable; otherwise, there might be delays in checking out licenses.
Full-Text Search server


ClearQuest Web client is independent of the license server; therefore, it does not need to be on the same host. Optimal connectivity to the license server is desirable; otherwise, there might be delays in checking out licenses.
License server


ClearQuest Web and CM Server:

Report Server for ClearQuest and Report Server for Crystal Reports

Use the Report Server for ClearQuest is for BIRT or Crystal Reports data-pull reports, and the Report Server for Crystal Reports for data-pull and data-push reports.For more information than is contained in this section, see Planning a deployment configuration for the Report Server for ClearQuest. The Report Server for ClearQuest can be deployed on Windows and Linux. However, the Report Server for Crystal Reports, which supports execution of data-push and data-pull reports, must be installed on Windows.

If you want to use the Report Server for ClearQuest to manage Crystal data-pull reports, you must also install and configure the Report Server for Crystal Reports on the same server to be able to run Crystal data-pull reports. At runtime, the Report Server for ClearQuest extracts Crystal data-pull reports to the file system, and the report is launched on the Report Server for Crystal Reports.

The Report Server for ClearQuest can be installed the same place that it is hosted, because it uses its own instance of the WebSphere Application Server. Also, it can be installed on the same host as ClearQuest Web, CM Server, and Full-Text Search. However, it requires that a CM Server be installed before completing configuration of the report server. The CM Server does not need to be on the same host.

Recommended free disk space with CM Server is as follows for the operating systems specified:

  • Windows 2003 SP2: 500 MB
  • RedHat Enterprise Linux AS 5.0 Update 1 and Update 2 or SuSE Linux Enterprise Server 10.0 SP1, SP2: 500 MB

Technically it can be installed on an existing WebSphere Application Server, but the Installation Manager does not enable this type of installation.

Full-Text Search server

The Full-Text Search feature can be:

  • Deployed on Microsoft® Windows®, UNIX®, or Linux®
  • Installed on its own host, because it has its own WebSphere Application Server instance
  • Installed on the same host as ClearQuest Web, CM Server, and Report Server
  • Installed on an existing WebSphere Application Server, which allows use of an existing WebSphere Application Server infrastructure
  • Deployed to multiple WebSphere Application Server profiles (each profile handles indexing of only one ClearQuest user database)
  • For maximum indexing performance, the index should reside on a nonsystem disk that rotates at 10,000 RPM or greater. Maximum performance is not required unless you need submillisecond response time on queries.
  • A ClearQuest FTS index will be dramatically smaller than a ClearQuest user database because it is storing only a dictionary of terms that are identified and referenced by pointers.
  • ClearQuest FTS logs in to your ClearQuest database to retrieve records. Every time it logs in (typically every 10 minutes), it uses a ClearQuest license and then releases it upon closure of the session.

Recommended disk space:
FTS uses the Lucene index, which will grow slowly as your ClearQuest database grows. After the initial batch indexing is completed, make sure that there is twice as much free disk space as the Lucene index size. This is required to run a successful optimization on the Lucene index.

Toplogy planning guidelines

General guidelines:

  • When practical in your environment, having many servers with the same configuration will simplify your deployment.
  • You might want to isolate a particular component on a system so that the system going down will not affect the rest of your deployment. For example, you could configure Full-Text Search on its own system. Then, if the Full-Text Search server is not available, there is no impact on the rest of your system.
  • If Reporting is supported on your platform but will not be used often, you can install Reporting on all Web servers. The advantage is that the cost of this method is low.
  • Rational ClearQuest supports the use of virtual machines. Some installations have the entire infrastructure on virtual machines.

Load balancing and bottlenecks to consider

The need to balance loads depends on many factors, most of which will be dictated by the environment and needs of the deployment. These are factors to consider:

  • Number of users
  • Complexity of the schema
  • Types of functions users perform

Example 1: The schema is very complex, with many record types and hooks. The 4 GB Web servers, 4xCPUs, show consistent response time for about 60-70 concurrent users. If the number of concurrent users exceeds 100 and there is performance degradation, this would be a candidate for load-balancing.

Example 2: The schema is moderately complex, with few record types and hooks. The 4 GB Web servers, 4xCPU, with consistent response time for 100+ concurrent users. In this case, there is no need to load balance if your usage requirements are being met.

Most of the load balancing setup occurs on the server side. For more information, see the Information Center section on Setting up a load balancing configuration and the developerWorks page on Performance Resources for IBM Rational ClearCase and ClearQuest.

Criteria for distributing components to different servers

These are several things to consider when you deciding how to distribute components across different servers.

Cost of downtime

Example: A deployment where ClearQuest Web is deployed on only one server; therefore, if that server goes down, the impact of downtime will be great.

Cost of servers

Example: A new release of software might require more hardware than is available. In this case, virtual machines are a good option because they are cost-effective and easier to maintain.

To simplify setup and maintenance:

The use of virtual machines can provide benefits in the consolidation of systems.

Example: Use of VMware ESX servers

Before upgrading

Before installing Rational software with IBM Installation Manager, you must use the rationaluninstalltool.exe tool to uninstall previous versions. The previous versions were installed using Windows MSI-based installation technology; therefore, they need to be uninstalled by using this tool.

If your Rational product is installed on a Linux or UNIX system, you must uninstall the product before upgrading to the next version with IBM Installation Manager. You can uninstall your current version with the uninstall option of install_release.

Hardware planning

In addition to the existing features available with ClearQuest, special consideration of RAM and secondary storage space should be taken to ensure sufficient processing power for the following new components, whether they are on one host or many hosts.

  • Change Management Server
  • Report Server for ClearQuest (supports both BIRT and Crystal Reports using data-pull searches)
  • ClearQuest Report Server for Crystal Reports
  • ClearQuest Full-Text Search profile (one WebSphere Application Server profile per user database, separate RAM dependency for each profile)

For information about hardware, software, and supported platforms, see CM Server hardware and software requirements.

For information about database requirements, see Supported Database Servers for a ClearQuest 7.1 environment.

Software planning for general network requirements

Note:
The following requirements have not changed in Rational ClearQuest 7.1, although, with the new features, there might be less need for using the LAN-based ClearQuest desktop clients.

The following ClearQuest clients support Local Area Network (LAN) access only.

  • ClearQuest for Windows, ClearQuest Client, and ClearQuest Client for Eclipse
  • E-Mail Reader
  • ClearQuest API core-based scripts
  • ClearQuest Web server components

All require LAN access relative to the production database server.Wide Area Network (WAN) access is supported through the ClearQuest Web client interface, connecting with a Web browser to a ClearQuest Web server. See Using ClearQuest over a WAN.

Upgrade planning

Detailed planning is suggested when an upgrade is required from a previous version of Rational ClearQuest 7.1. These are some of the steps to follow and the locations of the detailed information:


Back up your data and configuration

To create a backup version of all of your data and any configuration information, follow the steps for Planning your upgrade.


Test your environment

Make sure that your test environment and all applications are working as expected. Then test all the tools before going live.


Install software

IBM Installation Manager is a single installation technology for many IBM Rational applications. Installation Manager is a program that installs, updates, and modifies packages. It helps manage IBM applications (or packages) that it installs. After installation, it helps you keep track of what was installed and determines what is available to install. Installation Manager replaces Windows MSI and UNIX or Linux install_release-based installers that were previously used.

For an overview of all installation tasks, see Installing Rational ClearQuest.

For information regarding the options and limitations for Silent installation, or for Enterprise or Silent installations, see Installing silently.


Configure specific features

Administrators are required to perform post-installation configuration tasks based on the components that were selected during the installation.

Rational ClearQuest Web

Rational ClearQuest Web is a browser-based interface to Rational ClearQuest that runs on Windows, the UNIX system, and Linux. You can track defects and change requests in Rational ClearQuest Web. When a session times out, you can re-authenticate and then continue where you left off; the user interface state is not lost. Users can perform multiple tasks at the same time. Example: You can run a query, then start working on a defect while the query is running in the background.

For more information about how to configure and customize ClearQuest Web, see Administering Rational ClearQuest Web.

Change Management Server

The Change Management (CM) Server is a unified application server for both ClearQuest Web and ClearCase Remote Client. It leverages the performance, security, and scalability of WebSphere Application Server. The CM Server default configuration is suitable for most sites, but some sites might need to modify the CM Server configuration after an installation to accommodate various host or site-specific requirements. For example:

  • To change CM Server HTTP port numbers
  • To change CM Server logging defaults
  • To configure access to CM Server from another WAN server acting as a proxy

Table 3 shows site configuration options to specify. For more information, see:

Table 3. ClearQuest Web CM Server configurable options within ClearQuest Web
Site configuration
Security OptionsSession Timeout (seconds)1,800 (default)
Application OptionsServer Work Thread Count (number)16 (default)
CM Server OptionsActive ClearQuest Session Threshold (number)30 (default)
Report OptionsMaximum Active Servers (number)8 (default)
Email OptionsRecycle Server Session Limit (number)200 (default)
Recycle Server Lifetime Limit (seconds)86,400 (default)
Recycle Server ONC RPC Call Limit (number)100,000 (default)

Figure 1 illustrates these and other subordinate components on the on the IBM HTTP Server and the workflow:

  • CM Profile
    • ClearQuest Web
    • CM Server
  • Report Profile
    • Report server
  • ClearQuest (CQ) Search Profile
    • Full-Text Search (FTS) server
Figure 1. Overview of ClearQuest Web architecture installed on a server host
Diagram of path from browser to database

Note:
Each profile is a separate instance of WebSphere Application Server. Each instance can be deployed into an existing WebSphere Application Server environment. By default, IBM Rational ClearQuest deploys a WebSphere Application Server environment that is configured with these three profiles: CM, Report Server, and ClearQuest Search.

Many CM Server attributes affecting ClearQuest Web performance can be configured in Site Administration CM Server options.

Reporting: Enhanced, flexible, "pull-data" reporting

Rational ClearQuest 7.1 supports both the “data pull” and “data push” models of reporting.

  • Data push means that Rational ClearQuest is responsible for generating the reports and pushes the data to the reporting component for layout.
  • Data pull means that the reporting component is responsible for generating the reports and pulls the data from Rational ClearQuest. The data pull model provides enhanced flexibility and capabilities over the traditional ClearQuest data push model.

Traditional data push for Crystal Reports

Previous releases of Rational ClearQuest, such as Version 7.0, included the Crystal Reports runtime components that enabled the ClearQuest client and the ClearQuest for Windows client to run Crystal Reports. Rational ClearQuest Version 7.1 no longer includes the Crystal Reports runtime components. If you choose to use data push with Crystal Reports, there are two options for deployment. For more information, see Designing, editing, and running traditional data-push reports.

To set up data push reporting for Rational ClearQuest Web 7.1, you need to deploy the Java™ Reporting Component (JRC) for Crystal Reports data execution on ClearQuest Web. The Report Server for Crystal Reports component must be installed before you follow these steps for configuring the JRC runtime component: Configuring the ClearQuest Report Server for Crystal Reports.

This same Web server-based component for data-push execution of Crystal Reports on ClearQuest Web (JRC runtime) can also be used for remote execution within Rational ClearQuest 7.1 client rather than using the Crystal Reports Report Design Component (RDC) installed locally. For more information, see Configuring the Eclipse clients to run Crystal Reports on the server.

Data pull reporting for Crystal Reports and BIRT

For information about preconfiguration requirements before designing a data-pull Crystal Report, see Configuration tasks before designing Crystal Reports data-pull reports.

For information about sharing and running data-pull reports using the Report Server for ClearQuest (Crystal Reports or BIRT reports), see About the Report Server for ClearQuest.

BIRT reports on the local file system can be opened and executed by using the BIRT perspective of the Rational ClearQuest for Eclipse client. The Report Server for Rational ClearQuest is used to manage data-pull reports in a shared report repository.

Note:
BIRT does not require a Feature Level upgrade. It can be used while there is a single Version 7.1 CM Server with a Report Server profile enabled.

Full-Text Search

With this feature a ClearQuest Web user can search any ClearQuest record using natural language queries, just like using a Web based search engine. By default, Full-Text Search (FTS) is not configured.

Requirements (choose one):

  • Feature Level 7 user database (with or without Rational ClearQuest MultiSite)
  • Feature Level 5 or 6 with IBM® Rational® ClearQuest MultiSite® replicated user database

ClearQuest Full-Text Search has some in-depth configuration steps that must be performed for each user database. These steps configure the underlying technologies for the open source Apache Software Foundation Solr enterprise server search engine and the Lucene index for use with Rational ClearQuest.

For a full description of the Full-Text Search feature, the engine behind it, and a step-by-step guide on how to configure, enable and disable, maintain, and diagnose ClearQuest Full-Text Search, see Configuring and maintaining Full-Text Search in the ClearQuest Information Center.

Important:
Follow the steps in the exact order specified.

Note:
When using Rational ClearQuest MultiSite replicas, you must either deploy ClearQuest Full-Text Search services at each site or plan a single-index or multiple-site deployment.

Feature Level 7

Feature Level 7 is the default (optional) when you create a new schema repository with the Maintenance Tool. With Feature Level 7, you can enable the Pessimistic Record Locking feature, use Full-Text Search (without ClearQuest MultiSite) and use FIPS 140-2 approved cryptography. See the ClearQuest Information Center for more information about feature levels.

Federal Information Processing (FIPS) 140-2 approved data encryption

Rational ClearQuest 7.1 supports enhanced security by using Federal Information Processing Standard (FIPS) 140-2 approved data encryption algorithms. FIPS 140-2 is the U.S. government computer security standard used to accredit cryptographic modules. FIPS 140-2 includes a list of approved cryptographic algorithms and describes approved modes of operation.

For more information about how to use FIPS 140-2 approved algorithms, see the Configure FIPS 140-2 approved data encryption section of the ClearQuest Information Center.

Notes:

Optimistic and pessimistic record locking

There are two models for locking data in a database:

  • Optimistic locking, where a record is locked only when changes are committed to the database. By default, ClearQuest uses optimistic record locking.
  • Pessimistic locking, where a record is locked while it is edited.

Note:
Enabling pessimistic locking requires Feature Level 7. After the schema repository and associated user databases are at Feature Level 7, the database will not be accessible using ClearQuest clients or servers earlier than version 7.1.

For more information, see Optimistic and pessimistic record locking in the Information Center.

Multiple LDAP configurations

Rational ClearQuest 7.1 introduces support for environments where multiple LDAP configurations can be used for authentication. The details for the multiple LDAP configurations can be found in the command syntax for each of the LDAP commands.

For more information about LDAP configurations, see Installing and upgrading in the Information Center.

Logging for monitoring and debugging

You can use logging for monitoring and debugging CM Server- and CM API-based applications. Logging tracks CM Server and CM API user operations and errors that occur while a CM Server or CM API-based application is running.

For more information, see Configuring logging.

Result set limitations

This feature limits the server load and reduces the waiting time for large query sets. Review the documentation to see whether this configuration is appropriate for your environment, because it might not be in some cases.

For more information about result set limitations, see Configuring query limits on result sets.

Disable or re-enable Remember Password

With this feature, both Rational ClearQuest client and ClearQuest client for Eclipse display the option to save passwords across user sessions when connecting to a database in the specified database set.

For more information, see the ClearQuest Information Center.

Application lifecycle management (ALM) packages and ALM schema

The included ALM packages and the ALM schema provide help ensure that you use ALM best practices in your new or existing Rational ClearQuest change management system. Administrators can define roles and processes for each project, as well as security policies to allow access to projects.

For background and guidance regarding the new ALM schema, see this Rational Edge series:

Application lifecycle management with ClearQuest 7.1.0.0: Part I

Application lifecycle management with ClearQuest 7.1.0.0: Part 2

Application lifecycle management with ClearQuest 7.1.0.0: Part 3

Download the ALM tutorial from developerWorks: Rational ClearQuest Application Lifecycle Management packages for ClearQuest 7.0.1* (see the Download link at bottom of the page).

*Note:
The ALM packages can also be applied to Rational ClearQuest Version 7.0.1.

Spell-checking in the Rational ClearQuest for Eclipse client

Rational ClearQuest provides a spell-checking capability in the Eclipse client (integrated development environment, or IDE, and rich client platform(RCP)). It supports the IBM Group 1 languages that are supported by LanguageWare:

  • English
  • French
  • German
  • Italian
  • Portuguese (Brazilian)
  • Spanish

This feature does not support these languages:

  • Chinese, simplified or traditional
  • Japanese
  • Korean

With this feature, you can:

  • Enable or disable real-time spell checking
  • Choose the dictionary to use for spell-checking
  • Specify rules for ignoring certain, predefined sequences (dates, times, capitalization)
  • Add words to a user-defined custom dictionary.

Other areas that require attention

Upgrading to Feature Level 7

There are multiple reasons for upgrading a ClearQuest environment to Feature Level 7, but these are the primary reasons:

  • Ability to use ClearQuest Full-Text Search without MultiSite
  • Ability to enable Pessimistic Record Locking
  • Ability to enable FIPS encrypted passwords.

For more information, see Features in the Feature Levels.

To perform a Feature Level upgrade, see Changing the feature level and metaschema version.

Note:
After you have upgraded to Feature Level 7, you will not be able to connect to ClearQuest clients or servers earlier than Version 7.1. It is a good idea to make a backup copy and then upgrade the copy before upgrading your production version.

Performance

For fine-tuning and other performance issues, see:


Frequently asked questions

Should the license server be on a machine by itself?

There are benefits to having the license server on a separate machine. For example, it is not affected by maintenance of other applications. You might also consider redundant license servers so that users will have available license servers to connect to. License server hardware requirements are not as extensive as that of other Web servers (see License server setup. Example: If the license server is with other application servers, and you need to do maintenance on any of the combined servers, the license server could become unavailable to other applications.

Do we need a separate server for reporting?

No, reporting does not need to be on a separate server.

The report servers (both the report server for ClearQuest and the report server for Crystal Reports) can be on a shared resource with other server applications. Some of the considerations for deciding whether the report servers should be on separate systems are based on the volume, frequency, platform, and complexity of reports. See different Reporting topology requirements mentioned earlier in this article.

Can the Report Server and License Server be on the same machine?

Yes, report Servers and License servers can be on the same host.The license server can be on a system with other server applications running. Read about Report Server requirements (mentioned earlier in this article) and make the best decision for your environment.

Can the Report Server and ClearQuest Web and CM Server be on the same machine?

Yes, Report servers can be on the same host as ClearQuest Web and CM Servers.Read the Report Server and ClearQuest Web and CM Server requirements (mentioned earlier in this article) and make the best decision for your environment.

Can the Report Server and Full-Text Search be on the same machine?

Yes, Report Servers and FTS servers can be on the same host.If the machine where these servers are deployed is close to the minimum disk or RAM requirements, then they should be reconfigured. Read the Reporting and FTS topology requirements (earlier in this article) and make the best decision for your environment.

Do you need a separate server for Full-Text Search?

No, Full-Text Search (FTS) does not need to be on a separate server. Read the Full-Text Search server requirements, and make the best decision for your environment. Example: In a multiple site environment, you can use one FTS server for several replicas rather than each replica having its own FTS server on a separate machine. Because there are several manual steps for FTS setup, it might be easier to have a common server for several replicas. Performance should be considered with remote replica to a local FTS server.

Can FTS Server and License Server be on the same machine?

Yes, FTS Servers and License servers can be on the same host.The license server can be on a system with other server applications running. Read the license server and reporting requirements and make the best decision for your environment.

Can FTS Server and the ClearQuest Web and CM Servers be on the same machine?

Yes, the FTS server can be on the same host as ClearQuest Web and CM Servers.Read FTS Server and ClearQuest Web and CM Server requirements (mentioned earlier in this article) and make the best decision for your environment.


Acknowledgements

Many thanks to colleagues who contributed to this article:

  • Sandy Roschelle
  • David P. Sampson
  • George Aroush
  • Bryan Hogan
  • Yuhong Yin

Resources

Learn

Get products and technologies

Discuss

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into Rational software on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Rational
ArticleID=427511
ArticleTitle=Deployment Planning for IBM Rational ClearQuest Version 7.1
publish-date=09172009