Rational product deployment solution-CQ, CC, and DOORS

Document directory

• 3.1.1. Hardware
• ClearCase (including VOB Server and View Server)
• ClearQuest (including databases)
• Doors
• 3.1.2. Support Software (General)
• 3.2.1. Hardware
• 3.2.2. Support Software
• 4.1.1. ClearQuest Application Deployment
• 4.1.2. Database Server deployment
• 4.2.1. Primary Domain Server PDC
• 4.2.2. ClearCase Application Deployment

 

1. Introduction to rational 1.1. ClearQuest

Rational ClearQuest is a highly flexible defect and change tracking system for any platform,

Various types of changes are captured in any type of project. ClearQuest uses industry-standard databases, so it supports large and small projects. It also has a fully customizable interface and workflow mechanism that can be applied to any development process. It is combined with other development solutions (including configuration management, automated testing, and requirement management tools), allowing all team members to invest in defect and change tracking.

In addition to quick deployment, Rational ClearQuest can adapt to any process, business rules, and naming conventions required. You can also use ClearQuest pre-defined processes, forms, and related rules, or ClearQuestDesigner to customize-almost all aspects of the system can be customized, this includes status transition lifecycles, database fields, user interface la S, reports, charts, and queries for defects and change requests.

1.2. ClearCase

IBM Rational ClearCase is the forerunner in the field of software configuration. It is mainly based on Windows and UNIX development environments, it also provides comprehensive configuration management, including version control, workspace management, establishment management, and process control.

Rational ClearCase is an excellent software version control tool and software resource configuration management tool in the industry. During software development, using ClearCase for version control can achieve real-meaning parallel development and improve development efficiency. At the same time, as a commercial software, ClearCase is constantly evolving to meet the various needs of developers.

1.3. DOORS

DOORS is a comprehensive and powerful demand management tool that can work for different people at different stages throughout the software lifecycle (for example: project managers, system analysts, developers, and end users) provide requirements description, identification, and management, and support multiple users to manage large and complex projects in parallel.

DOORS provides a comprehensive solution for demand management. It provides three environments for editing requirements: document or table-based database environments (DOORS) and Internet-based Web environments (DOORSnet), MS Word-based environment (DOORSrequireIT ). DOORS can capture, connect, track, analyze, and manage information to ensure that the implemented project is consistent with the Requirement Specification Description and standards.

It provides all the features you need to capture, track, and manage user needs. The WORD-like interface can be used to directly input requirements in DOORS.

You can also import requests from files in multiple formats to the DOORS. These formats include:

· Microsoft Word, Excel, PowerPoint, and Outlook

· Common (ASCII) Text

· Rich Text Format (RTF)

· FrameMaker

· Interleaf

Once you have captured your needs in DOORS, you can use multiple features throughout the project lifecycle, such as view, link, and trackability analysis, to track and manage them.

 

2. Using three types of software can bring multiple conveniences to information project management. 2.1. You can customize the required business processes.

1. We can use ClearQuest to pre-define (built-in) processes, forms, and relevant rules, such as the defects and change tracking features mentioned in the preceding overview.

2. in addition to the predefined ClearQuest process, ClearQuest Designer provides powerful process customization functions, allowing you to customize almost all the business processes you want, custom content includes status transfer lifecycle, database fields, user interface layout, reports, charts, and queries of business requests.

2.2. control routine work documents and code

1. doors is mainly used as a tool for requirement development, requirement management and tracking in project implementation. Its interface style is similar to the word we use in daily use. During requirement development, doors can be used to record requirements, after the requirement is confirmed, you can use doors Association to associate the requirement with the design. After integration with ClearCase, the setting can be associated with the Code. The above method can be used to track the requirements and ensure the consistency and authenticity of the requirements.

2. Using clearcase, You can implement version control and change control for routine work documents and codes in project development to ensure the integrity of work documents and codes.

ClearCase can automatically track changes to each file and directory, and supports parallel development through the branch and merge functions. In the software development environment, ClearCase can also specify each object type (including source code, binary files, directory content, executable files, documents, test packages, compilers, and library files) implement version control and help the team establish a secure and reliable version history for each type of information they process when developing software, you can obtain the previous version by accessing the history. In ClearCase, you can also use permission control to prevent confidential files from being viewed or modified by others.

2.3. ClearQuest and ClearCase integration make independent development smoother

When we mention the integration of ClearCase and ClearQuest, We must describe the Unified Change Management (UCM). UCM is the third-generation Configuration Management Solution of IBM Rational, it is the "best practice" process used to manage all changes in software development from requirement acquisition to version release. UCM defines an activity-based code change management mode that can be immediately used for software development projects.

The configuration management tool ClearCase adopts the UCM integrated with the change management tool ClearQuest to achieve unified management of changes and configuration management, and supports code reuse using components, use the development stream and integration stream to support the ordering of branches.

If there is no application integration method in project development, a developer needs to find the Code related to the change after receiving the change request, and then modify the code one by one, if the developer has a good habit, he will record the Code he modified. If not, it is quite difficult to trace or maintain the code later. If you use the integration method, developers only need to associate the change request in ClearQuest to an activity in ClearCase. When the developer modifies the code, select the modified Code file and associate it with this activity, so that the change request-> activity-> code will be clearly associated, developers are more aware of what they need to do and how to do it, which saves a lot of time.

Figure 1. UCM

3. Requirements for software and hardware environments 3.1. Server 3.1.1. Hardware ClearCase (including VOB Server and View Server)

Device Model
Device quantity
Single Configuration Requirements	CPU: 2 GHz or above Memory: 4 GB or more Hard drive: more than 100 GB
Other requirements	The host of the master Domain Controller requires good performance and high stability. You can select hardware resources based on the number of domain users in the company. The network environment must be basically stable. Internal and external networks should be physically prevented, such as physical firewalls, routers, and proxy servers. Set the gateway and DNS of the master domain controller as the IP address of the master domain controller, and set the static IP address for each machine.

ClearQuest (including databases)

Device Model
Device quantity
Single Configuration Requirements	CPU: 2 GHz or above Memory: 4 GB or more Hard drive: more than 100 GB

 

Doors

Device Model
Device quantity
Single Configuration Requirements	CPU: 2 GHz or above Memory: 2 GB or more Hard Disk: 40 GB or more

 

3.1.2. Support Software (General)

Currently, the description of windows is provided, and linux and unix systems are supported.

Software requirements	Detailed requirements
Operating System Supported rational Software Versions: Clearcase 7. 1 .*, Clearquest7.1 .* Docker 9.3	Windows 7 Professional Edition SP1 Windows 7 Enterprise Edition SP1 Windows 7 Ultimate Edition SP1 Windows Server 2008 R2 Standard Edition SP1 Windows Server 2008 R2 Enterprise Edition SP1 Windows Server 2008 R2 DataCenter Edition SP1 Windows Server 2008 Standard Edition SP2 Windows Server 2008 Enterprise Edition SP2 Windows Server 2008 DataCenter Edition SP2 Windows Vista Business, Enterprise and Ultimate Editions SP1/SP2 Windows Server 2003 Enterprise Edition SP1/SP2 Windows Server 2003 R2 Edition SP1/SP2 Windows Server 2003 Standard Edition SP1/SP2 Windows Server 2003 Web Edition SP1/SP2 Windows XP Professional SP2/SP3 Windows 2000 Advanced Server SP4 Windows 2000 Server SP4
CQ Database	SQL Server 2008 R2 SQL Server 2008 SP1, SP2 SQL Server 2005 SP1, SP2, SP3, SP4 SQL Server 2000 SP2, SP3, SP4 Oracle 11g Oracle 10.x In Oracle 9.2 Dtplus 9.7 Dtplus 9.5 DB2 Express-C 9.5 IBM DB2 Express 9.5 DB2 Enterprise Edition 9.5 DB2 Express-C 9.1 IBM DB2 Express 9.1 DB2 Enterprise Edition 9.1 UDB 8.2.x UDB Components for Rational Products v8.2 Microsoft Access 2003 SP1
Browser	IE6.0 or above Firefox 2.0 or above Mozilla 1.6 or above Safari 1.2.3 or later
Other requirements	Domain Controllers can only be installed on Windows NT Server operating systems, such as Windows NT, Windows 2000 Server, Windows 2000 Advance Server, and Windows Server 2003 Enterprise. As a domain controller, it must be highly stable and secure. Therefore, it is not recommended to install any applications on the domain controller. Anti-virus software is required, but do not install security software for firewall and other control ports.

3.2. Client 3.2.1. Hardware

Device Model
Device quantity
Single Configuration Requirements	CPU: 2 GHz or above Memory: 1 GB or more Hard Disk: 40 GB or more

3.2.2. Support Software

Software requirements	Detailed requirements
Operating System	Windows 2000 Professional SP2/3 Windows Terminal Server on Windows 2003 Server R2 (Standard or Enterprise) Windows Terminal Server on Windows 2008 Server R2 (Standard or Enterprise) Windows XP Professional SP1/SP2/SP3 Windows Vista (Business or Enterprise) SP2 Windows 7 Professional Windows 7 Ultimate
Browser	IE6.0 or above Firefox 2.0 or above Mozilla 1.6 or above Safari 1.2.3 or later
Others	Eclipse 3.5
Clearcase plugin	Com.rational.clearcase.win32-v201102110950.zip
Clearquest plug-in

 

4. Deployment planning 4.1. ClearQuest4.1.1. ClearQuest Application Deployment

ClearQuest Web and CM Server must be installed on the same Server. Full-Text Search and ClearQuest Report server can be installed on the same Server as ClearQuest Web and CM server.

 

We recommend that you set up a single application with ClearQuest Web, CM Servers, ClearQuest Report server, and Full-Text Search. This deployment method can meet the needs of most functional applications of clearquest.

 

4.1.2. Database Server deployment

The database and the clearquest application can be deployed on the same server. We recommend that you deploy a separate database server for CQ for the sake of increasing record data and maintenance.

 

4.2. ClearCase4.2.1. master Domain Server PDC

PDC (Primary Domain Controller) is used to provide logon authentication for ClearCase users in Windows NT. All ClearCase users log on to the NT domain, that is, the PDC. We do not recommend that you install ClearCase on the PDC. the PDC should be configured with a separate machine.

 

We recommend that you set up a single PDC to facilitate unified management of the entire unit.

4.2.2. ClearCase Application Deployment

The VOB Server saves the physical storage of VOB. The number of VOB servers can be one or multiple, which should be determined according to the specific project. VOB Server not only requires good stability for hardware machines, but also high performance requirements. The larger the machine memory, the better the performance. If the VOB capacity increases, the memory size should also increase accordingly.

Registry Server is used to record the storage path and tag Information of VOB and VIEW. When you access VOB through a View, you actually first go to the Registry Server to find the physical storage location of VOB before accessing VOB. The Registry Server requires good hardware stability.

The View Server saves the physical storage of the View. The number of View servers can be greater or less. Generally, large enterprises and institutions have such servers. View Server requires sufficient hard disk space for hardware.

The Registry Server, VOB Server, and View Server can be set on one Server. If you have conditions, we recommend that you set View Server and VOB server on different servers, and do not run other programs on the VOB Server.

4.3. Doors

Compared with ClearQuest and ClearCase, Doors has simple applications and has low performance requirements on servers. However, it requires good hardware stability. We recommend that you set up a single Doors server.

4.4. Client

The Client refers to the work environment of developers, testers, and integrators. Generally, Windows NT/2000 Client, Windows XP, and UNIX Client are divided by operating system. Currently, clent meets the requirements of using ClearCase. The faster the network, the better.

4.5. License Server

The License Server is responsible for managing floating licenses. When the client performs an operation, the system will first apply for the License from the License Server and obtain the License before the operation is allowed. The client retains the License for a period of time. If there is no clearquest or ClearCase operation during this period, the system automatically releases the License for other users. The License retention time can be set. The default value is 1 hour, and the minimum value is 30 minutes. In a floating License system, the more users share a License server, the more economical it is. The only restriction is the region and network distribution. The License Server requires good hardware stability and has no high requirements on machine performance.

We recommend that the entire Organization have a License Server.