KR20100125922A - Integration system and method of perforce server and clearquest server - Google Patents

Abstract

PURPOSE: An integration system of a shape change management tool and a method thereof are provided to secure the integrity of data by automatically processing an error and perform two-way synchronization between the management of change tool and the shape manager tool. CONSTITUTION: A perforce server(1) is a shape management tool. A ClearQuest server(2) is a modification management tool. An integration gateway server(3) periodically reads out a detail stored in an integration data repository and synchronizes job solution information to ClearQuest API and Perforce API in a perforce server.

Description

 Linkage system and method of configuration management tool and change management tool {INTEGRATION SYSTEM AND METHOD OF PERFORCE SERVER AND CLEARQUEST SERVER}

The present invention relates to a linkage system between a configuration management tool and a change management tool, and more particularly, a configuration management tool and a change suitable for tracking and managing changes to development sources by defining correlations between tools and linking data therebetween. A system and method for linking management tools.

In the software management system, if the shape information and the change information are not linked and managed separately, the association of the reason (defect, change request, etc.) for the source change history cannot be tracked. In other words, it is not possible to check which source file has been modified for the change request history, and it takes a lot of effort and time to resolve similar defects. When the verification (review, test, etc.) of the changed source code is required, the relevant team You will have difficulty communicating.

    For this reason, various solutions for configuration-change management linkage are being used, and in case of using IBM's ClearCase (CC) and ClearQuest (CQ), the interlocking system provided by IBM or In order to improve the speed, a user-developed linkage system was used.

   However, in recent years, by switching Clearcase to Perforce, a commercial configuration management system, two-way synchronization is possible between Perforce and ClearQuest without being affected by the existing environment, and automatic reprocessing of errors occurred during linkage There is a need to link Perforce and ClearQuest to ensure the integrity of inter-data.

The conventional linkage method between Perforce, a configuration management tool, and ClearQuest, a change management tool, supports only one-way synchronization of Perforce's Job through ClearQuest's hook.

Therefore, since only one-way synchronization from ClearQuest to Perforce is possible, Clearquest cannot track changes made in Perforce. In addition, the linkage function provided in the form of schema is designed in a structure using linkage of ReleasePro, and has its own schema design. For this reason, if you do not consider the linkage with Release Pro, you cannot apply the functions provided and have difficulty in setting and maintaining mapping items between Perforce-ClearQuest.

Accordingly, if an error occurs due to a mismatch between items of Perforce-ClearQuest or no Perforce is installed during data linkage processing, only the failure message is output and then terminated. Because of this, there is a high probability that data inconsistency between ClearQuest and Perforce occurs, and the details are not managed at all.

Internally, it provides a function to show the detailed information of Perforce by connecting to P4DB through hyperlink, but it cannot be applied when there are multiple Perforce servers. In addition, when synchronizing data from ClearQuest to Perforce, there was a problem in that even if a plurality of Perforce servers exist, the function of showing detailed information present in Perforce could not be applied.

Accordingly, an object of the present invention is to enable bidirectional synchronization without affecting the existing environment between Perforce, a configuration management tool, and ClearQuest, a change management tool, and automatically reprocess errors that occur during linkage. It ensures the integrity of data so that it is easy to track or manage the change history of development source.

The objects of the present invention are not limited to the above-mentioned objects. Other objects and advantages of the invention will be more clearly understood by the following description.

The present invention for achieving the above object,

A perforce server for the source management program as the configuration management tool;

A clearquest server that makes it easy to implement various workflows and facilitates data integration and analysis as a change management tool;

Start periodically and read the contents stored in the linked data storage sequentially and synchronize job resolution information from the Perforce server to the ClearQuest server using the ClearQuest API and the Perforce API, or catch the Perforce server from the ClearQuest server. An interlocking gateway server for synchronizing and storing data;

Link the URL to the 'P4Change' record in the clearquest server so that the user can search or search for information on the job (clearquest record) and change list, and files and file contents and revisions related to each change list. It is characterized in that it comprises a; Web system to enable the history information search and comparison between revisions.

Another invention for achieving the above object is,

Perforce trigger of the Perforce server stores the details to be processed in the storage of the interlocking gateway server, and the interlocking program in the interlocking gateway server periodically monitors the storage to use the Perquest using ClearQuest API when there is a history to process. Synchronizing the job resolution information from the server to the clearquest server;

If an error occurs during data synchronization processing in the ClearQuest server, the error details are stored in the interlocking storage of the interlocking gateway server, and the interlocking program in the interlocking gateway server is periodically started to process the Perforce API when the processing history exists in the interlocking storage. Synchronizing data from the clearquest server to the job of the Perforce server by using;

The present invention basically allows the shape information and the change information to be linked, thereby ensuring the management and traceability of the source change history related to the change, improving the communication between related teams, and the release management system based on the linked information. There is an effect to facilitate the linkage.

   The web system can establish a linked system regardless of the existing environment of the Perforce server and the ClearQuest server, and can be linked even when multiple Perforce servers or ClearQuest databases are configured, and a firewall between the servers If it is cleared, the client may not be able to access the two servers, and the setting between the two servers can be managed in ClearQuest as XML, and the functions of the ClearQuest server are provided in package form without any significant effect on the existing system. It is effective to make system construction and maintenance easy.

   In addition, bi-directional data is synchronized through the interlocking gateway server, so that it can be processed quickly without waiting for the user, and automatically reprocessed when an error occurs during the connection, thereby ensuring the integrity of the data between the two systems, perforce and clearquest. If ClearQuest operates in a place where the data of the related items are inconsistent or the Perforce program is not installed, or when an error occurs when synchronizing from the ClearQuest server to the Perforce server due to a lack of network, etc. It is automatically processed by the interlocking program, and the processing history is managed so that it can be monitored.

    In addition, through the link of the web address connected to the specific change list of the ClearQuest server, information such as related files, file contents, revision history, etc. can be inquired and compared between revisions, and through the web system, Perforce server or ClearQuest Even non-users of the server can inquire information and obtain information in real time, thereby ensuring the reliability of the data, and based on such information, the release note information can be easily inquired and utilized.

The above objects, features, and advantages will be described in detail with reference to the accompanying drawings, whereby those skilled in the art may easily implement the present invention. In describing the present invention, when it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description will be omitted. Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram of a system for linking a configuration management tool and a change management tool according to the present invention. As shown in FIG. 1, a perforce server 1, a clearquest server 2, an interworking gateway server 3, And web system 4.

The linkage system as shown in FIG. 1 is designed in such a way that linkage is possible even when multiple databases of Perforce server 1 or ClearQuest server 2 are separated or geographically separated. For this purpose, the clearquest server 2 manages the information ('P4Server' record) of the perforce server 1, and the information of each perforce server 1 is 1: project and 'Project' record information. Have a relationship. Using this information, when creating / modifying / deleting a specific change item, the job is synchronized to the Perforce server 1 specified in the related project.

If a firewall is set between the Perforce servers (1) and the ClearQuest server (2), it is necessary to release the firewall for the corresponding port, and in order to minimize the firewall release and efficiently operate the interlocking gateway server ( 3) it is preferable to use the same server as the clearquest server (2).

When an event occurs in a client program, the synchronization is performed regardless of the operating system in the Perforce server 1 and the ClearQuest server 2, and in the Perforce server 1, synchronization is performed by a perforce trigger and cleared. In the quest server 2, synchronization is performed by a hook.

The interlocking gateway server 3 between the perforce server 1 and the clearquest server 2 is provided with an interlocking data store and an interlocking program. The interworking gateway server 3 periodically starts the interworking program and sequentially reads the details stored in the interworking data storage, synchronizes using ClearQuest API and Perforce API, and stores the processing result. do.

In the P4-CQ Integrator (4) that controls the system as a whole, a bidirectional process between the Perforce server (1) and the ClearQuest server (2) operates. The activities and flows operated by the force server 1 and the clearquest server 2 will be described with reference to FIGS. 2 and 3 as follows.

   First, when synchronizing job resolution information from the perforce server 1 to the clearquest server 2, the perforce trigger (p4 trigger) operated by the perforce server 1 is the interworking gateway server 3. Stores the details to be processed in the repository in (SA1, SA2).

    Subsequently, periodic monitoring is performed by the interlocking program of the interlocking gateway server 3, and if there are details to be processed at that time, data synchronization is performed using the ClearQuest API. (SA3-SA5)

   Through the above process, the data synchronization result (job resolution information) is reflected to the ClearQuest server 2. (SA6)

   In this case, when directly synchronizing data through the ClearQuest API, it is not immediately processed, but it takes some waiting time, so that it is processed by the interlocking gateway server 3 for faster processing.

   As a result of the experiment, when updating the data of the clearquest server 2, it is found that it normally takes 2-3 seconds only to connect to the ClearQuest session.

On the other hand, when synchronizing data from the clearquest server 2 to the job (Job) of the Perforce server 1, when the hook operation of the clearquest server 2 is started, the mapping information in the XML format Read and perform data synchronization using the Perforce API (SB1-SB3).

If an error occurs during the data synchronization process, the error details are stored in the interlocking storage of the interlocking gateway server 3. (SB4, SB5)

The above error may occur when the data of the link item between the Perforce server 1 and the ClearQuest server 2 is inconsistent or operates in a place where Perforce is not installed. have.

Thereafter, the interlocking program of the interlocking gateway server 3 is periodically started to perform periodic monitoring. When it is determined that the processing history exists in the interlocking storage, it is synchronized using the Perforce API. (Reprocess) and save the result. (SB6-SB9)

In other words, the job of the Perforce server 1 is directly updated (created / modified / deleted) through the Perforce API operated on the hook of the ClearQuest server 2, in which case, XML Data is linked based on predefined mapping settings in the form. When constructing the linked data, items are defined in a 1: 1 format in XML format based on a Perforce JobSpec and a ClearQuest Field.

The definition of the linked storage shown in FIGS. 2 and 3 and the related operations will be described in detail as follows.

Four interlocking tables (IF_P4CQ_JOB, IF_P4CQ_JOB_LOG, IF_P4CQ_CHANGE, and IF_P4CQ_CHANGE_LOG) are stored in the interlocking gateway server 3 to store details to be processed.

Table 1 below is an IF_P4CQ_JOB interface table that stores job information between the Perforce server 1 and the ClearQuest server 2. Here, Perforce Job information is changed according to the request type (Req_Type) by reading records in which the request status (Req_Status) is N (unprocessed) or E (error). Process using p4 job -i (create / modify), -d (delete) which are Perforce API.

Table 2 below is an IF_P4CQ_CHANGE interface table that stores connection / disconnection information of a job-changelist between the perforce server 1 and the clearquest server 2. Perforce Changelist information ('P4Change' record) of ClearQuest server 2 according to the request status (Req_Type) in order to read records with request status (Req_Status) of N (unprocessed) or E (error). Create and associate a record with a job. Process using ClearQuest API BuildEntity (record creation), EditEntity (record modification), AddFieldValue (link between records).

If the process is successful, the result is stored in the IF_P4CQ_JOB_LOG and IF_P4CQ_CHANGE_LOG tables. This log table has the same table configuration as IF_P4CQ_JOB, IF_P4CQ_CHANGE, and only the completion date information is added.

Since the processing history is managed through the interlocked data stores (Tables 1 and 2) as described above, the administrator can monitor what kind of processing has occurred, what is the cause of the error, and the processing result.

In another embodiment of the present invention, a web system (P4CQ-J) 4 is provided as a function for user convenience. Resolving specific change items (defects, change request details, etc.) by linking a URL for viewing detailed information of the change list in the web system 4 to the 'P4Change' record in the clearquest server 2. It provides the function to view the details of the modified source file for each change list generated. The user may access the web system 4 directly and inquire the desired information.

Thus, a user can provide convenience for inquiring information in the perforce server 1 and the clearquest server 2 without installing or accessing the perforce server 1 and the clearquest server 2. In addition, since a large amount of information is not duplicated and managed by the clearquest server 2, the information is inquired and displayed in real time, thereby ensuring the reliability of the information being inquired.

In addition, the user can search or search Job (ClearQuest Record) and change list information through the web system (4), and the file and file content and revision history related to each change list. history Information search and revision can be made. In addition, release notes stored and managed by the ClearQuest server 2 can be conveniently searched and searched on the web. As a result, the user can search the list and information of the changed items (defects, change requests, etc.) as well as the basic information of the release (project and version), and change list and source file details related to each change item at a glance. You can generate queries and reports in the.

Although the preferred embodiment of the present invention has been described in detail above, the scope of the present invention is not limited thereto, and may be implemented in various embodiments based on the basic concept of the present invention defined in the following claims. Such embodiments are also within the scope of the present invention.

1 is a block diagram of a linkage system of a configuration management tool and a change management tool according to the present invention;

2 is a flowchart illustrating information interworking from a perforce server to a clearquest server.

3 is a flowchart illustrating information linkage from a ClearQuest server to a Perforce server.

*** Description of the symbols for the main parts of the drawings ***

1: Perforce Server 2: ClearQuest Server

3: interlocking gateway server 4: web system

Claims (11)

A perforce server for the source management program as the configuration management tool; A clearquest server that makes it easy to implement various workflows and facilitates data integration and analysis as a change management tool; Start periodically and read the contents stored in the linked data storage sequentially and synchronize job resolution information from the Perforce server to the ClearQuest server using the ClearQuest API and the Perforce API, or catch the Perforce server from the ClearQuest server. An interlocking gateway server for synchronizing and storing data; Link the URL to the 'P4Change' record in the ClearQuest server so that the user can search or search for information on Job (ClearQuest Record) and change list, and files, file contents and revision history information related to each change list. Web system that allows comparison between inquiry and revision; Link system of the configuration management tool and change management tool, characterized in that consisting of. The method of claim 1, wherein the information ('P4Server' record) of the Perforce server managed by the clearquest server has a 1: 1 relationship with the project ('Project' record) information, and mapping information in XML format between the two servers. A system for linking a configuration management tool with a change management tool, wherein a job is synchronized to a Perforce server assigned to a related project when a specific change item is created / modified / deleted using this information. The system of claim 1, wherein the interworking gateway server is configured on the same server as the clearquest server in order to minimize firewall release and to operate efficiently. Perforce trigger of the Perforce server stores the details to be processed in the storage of the interlocking gateway server, and the interlocking program in the interlocking gateway server periodically monitors the storage to use the Perquest using ClearQuest API when there is a history to process. Synchronizing the job resolution information from the server to the clearquest server; If an error occurs during data synchronization processing in the ClearQuest server, the error details are stored in the interlocking storage of the interlocking gateway server, and the interlocking program in the interlocking gateway server is periodically started to process the Perforce API when the processing history exists in the interlocking storage. And a second step of synchronizing data from the clearquest server to the job of the Perforce server using the configuration management tool and the change management tool. 5. The method of claim 4, wherein four interlocking tables (IF_P4CQ_JOB, IF_P4CQ_JOB_LOG, IF_P4CQ_CHANGE, IF_P4CQ_CHANGE_LOG) for storing details to be processed are defined in the interlocking gateway server. 5. The method of claim 4, wherein the first step reads records in which the request status (Req_Status) is N (unprocessed) or E (error) from the IF_P4CQ_JOB interface table that stores job information between the Perforce server and the ClearQuest server. A system and method for linking a configuration management tool and a change management tool further comprising the step of changing Perforce Job information according to a request type (Req_Type). 7. The configuration management tool and the change management according to claim 6, wherein the change processing is performed using a perforce API p4 job -i (create / modify) or -d (delete) when changing the job information. How tools are linked. 5. The method of claim 4, wherein the second step includes a request status (Req_Status) of N (unprocessed) or E (error) in the IF_P4CQ_CHANGE interface table that stores connection / disconnection information of the job-change list between the Perforce server and the ClearQuest server. The method further comprises the step of reading the record in order to generate perforated change list information ('P4Change' record) of the clearquest server according to the request state in order and connecting with the record associated with the job (Job) How to manage configuration management tools and change management tools. 10. The method of claim 8, wherein the step of linking with a record connected to a job is performed using a ClearQuest API such as BuildEntity (record generation), EditEntity (record modification), AddFieldValue (link between records), and the like. Linkage system and method of the configuration management tool and the change management tool, characterized in that. 10. The configuration management tool according to claim 8 or 9, wherein when the processing of the step of linking with the record associated with the job is successfully completed, the processing result is stored in the IF_P4CQ_JOB_LOG and IF_P4CQ_CHANGE_LOG tables. Linkage system and method of management tool. 11. The system and method of claim 10, wherein the IF_P4CQ_JOB_LOG and IF_P4CQ_CHANGE_LOG tables have the same configuration as IF_P4CQ_JOB, IF_P4CQ_CHANGE and only the completion date information is added.

Images