JP7579229B2 - Synchronous control device, synchronous control method, and synchronous control program - Google Patents

Description

The present invention relates to a synchronization control device, a synchronization control method, and a synchronization control program.

Patent document 1 discloses a server device, an information processing method, and a program that can prompt server application upgrades in a data synchronization system, even in a configuration in which the server and client applications are not upgraded simultaneously (see paragraphs 0001 and 0035 of patent document 1, etc.).

JP 2018-45307 A

Now, there are several different ways to implement ERP (Enterprise Resources Planning), one of which is component-based ERP. The advantage of component-based ERP is that because management is separate for each system, it is possible to add and update the necessary versions when necessary.

However, because management is separate, there is a disadvantage in that it is difficult to guarantee consistency across the entire system. This disadvantage is particularly noticeable in events such as adding a new system later or upgrading each individual system. Although Patent Document 1 describes synchronization control through upgrades, the synchronization control method is limited to upgrading server applications.

The present invention has been made in consideration of the above problems, and aims to provide a synchronization control device, a synchronization control method, and a synchronization control program that can achieve the benefit of being able to separate management for each system while eliminating the disadvantage of the difficulty in ensuring consistency across the entire system.

In order to solve the above-mentioned problems and achieve the object, the synchronization control device according to the present invention is a synchronization control device having a control unit, and the control unit refers to a predetermined master, and checks whether there is a target business system to which the applied patch version identification information for the source business system has not been applied among the applied patch version identification information consisting of information for identifying patch versions that have been applied in the past and the business systems to which the patch version was created or provided and was applied, and if there is, it is characterized by having a DB object consistency check means that specifies the target business system to which the applied patch version identification information for the source business system has not been applied as a target to which the applied patch version identification information for the source business system is to be applied, a DB object synchronization means that applies the applied patch version identification information for the source business system to the target business system specified by the DB object consistency check means, a module consistency check means that compares a module master with a folder and checks whether there is a difference in file version or update date and time, and a module synchronization means that downloads the contents of the module master to the folder if the module consistency check means checks that there is a difference.

In the synchronization control device according to the present invention, the predetermined master is composed of an applied patch version master including the applied patch version identification information and a synchronization flag for the source business system, a common system script synchronization management master including the source business system and the destination business system, and a patch application history master prepared for each destination business system including the applied patch version identification information for the destination business system, and the DB object consistency check means acquires the applied patch version identification information for the source business system for which a flag indicating the need for synchronization is set from the applied patch version master, acquires the destination business system linked to the source business system constituting the acquired applied patch version identification information from the common system script synchronization management master, and if the applied patch version identification information for the source business system does not exist in the patch application history master for the acquired destination business system, identifies the acquired destination business system as the application target.

In addition, in the synchronization control device according to the present invention, the module master includes module identification data, a file version, and a file update date and time, the folder includes module identification data, a file version, and a file update date and time, and the module consistency check means checks for the existence of a difference when there is no file in the folder, or when the module master and the folder are compared and the module identification data is the same but the file version or the file update date and time is different.

In the synchronization control device according to the present invention, the module master is composed of a common system distribution module master, which is a master including module identification data, a file version, and a file update date and time, and stores modules of a common system; an AP module master, which is a master including module identification data, a file version, and a file update date and time, and stores modules of a business system used in an AP server; and a WEB module master, which is a master including module identification data, a file version, and a file update date and time, and stores modules of a business system used in a WEB server; and the module consistency check means compares the AP module master and the WEB module master with the folder, and at this time, when the same module identification data exists between the common system distribution module master and the AP module master and the WEB module master, the common system distribution module master and the folder are compared preferentially for modules identified by the same module identification data.

In the synchronization control device according to the present invention, the module master is composed of a common system distribution module master, which is a master including module identification data, a file version, and a file update date and time, and stores modules of a common system; an AP module master, which is a master including module identification data, a file version, and a file update date and time, and stores modules of a business system used in an AP server; and a WEB module master, which is a master including module identification data, a file version, and a file update date and time, and stores modules of a business system used in a WEB server; and the module synchronization means downloads the contents of the AP module master and the WEB module master to the folder, and at this time, if the same module identification data exists between the common system distribution module master and the AP module master and the WEB module master, downloads the contents of the common system distribution module master to the folder for modules identified by the same module identification data.

The synchronization control method according to the present invention is a synchronization control method executed by an information processing device having a control unit, and includes a DB object consistency check step in which, by referring to a predetermined master executed by the control unit, among applied patch version identification information for identifying patch versions that have been applied in the past and consisting of the business systems at the time of creating or providing the patch version and the target of the application, there is a target business system to which the applied patch version identification information for the source business system has not been applied, and if there is, the target business system to which the applied patch version identification information for the source business system has not been applied is identified as a target to which the applied patch version identification information for the source business system is applied; a DB object synchronization step in which the applied patch version identification information for the source business system is applied to the target business system identified in the DB object consistency check step; a module consistency check step in which a module master and a folder are compared to check whether there is a difference in file version or update date and time; and a module synchronization step in which the contents of the module master are downloaded to the folder if the module consistency check step checks that there is a difference.

The synchronization control program according to the present invention is a synchronization control program to be executed by an information processing device having a control unit, and is characterized in that it includes a DB object consistency check step for checking the existence of a target business system to which the applied patch version identification information for the source business system has not been applied, among the applied patch version identification information for identifying patch versions that have been applied in the past, which is information for identifying patch versions that have been applied in the past and is composed of the business systems to which the patch version was created or provided and was applied, by referring to a predetermined master, and if there is such a target business system, specifying the target business system to which the applied patch version identification information for the source business system has not been applied as a target to which the applied patch version identification information for the source business system is to be applied, a DB object synchronization step for applying the applied patch version identification information for the source business system to the target business system specified in the DB object consistency check step, a module consistency check step for comparing a module master with a folder to check whether there is a difference in file version or update date and time, and a module synchronization step for downloading the contents of the module master to the folder if it is checked in the module consistency check step that there is a difference.

The present invention has the advantage of being able to separate management for each system, while eliminating the disadvantage of the difficulty in ensuring consistency across the entire system.

FIG. 1 is a block diagram showing an example of the configuration of a synchronization control device. FIG. 2 is a diagram showing an example of an occurrence of an inconsistency in a DB server between a personnel system DB and a payroll system DB on the one hand, and an accounting system DB on the other. FIG. 3 is a diagram showing an example of an inconsistency occurring in the AP server and the WEB server between the personnel system DB and the payroll system DB, and the accounting system DB. FIG. 4 is a table showing an example of a management method, a synchronization control method, a synchronization timing, and a method of detecting an inconsistent environment for each of a module and a DB object. FIG. 5 is a diagram showing an example of a patch configuration. FIG. 6 is a diagram illustrating an example of the applied patch version master. FIG. 7 is a diagram illustrating an example of the common system distribution module master. FIG. 8 is a diagram illustrating an example of the common system script synchronization management master. FIG. 9 is a diagram illustrating an example of the patch application history master. FIG. 10 illustrates an example of an AP module master. FIG. 11 is a diagram illustrating an example of the WEB module master. FIG. 12 is a diagram showing an example of a flowchart of processing in this embodiment. FIG. 13 is a diagram showing an example of DB restoration when a business system is first introduced. FIG. 14 is a diagram showing an example of the master state in the DB server used in the module synchronization process when the business system is first introduced. FIG. 15 is a diagram showing an example of the state of folders in the AP server and the WEB server after module synchronization processing when the business system is first introduced. FIG. 16 is a diagram showing an example of a patch to be applied in a patch application process during a version upgrade (when a change is made to a DB object). FIG. 17 is a diagram showing an example of the state of the master in the DB server after patch application processing during version upgrade (when changes are made to DB objects). FIG. 18 is a diagram showing an example of a patch to be applied in a patch application process during a version upgrade (when a change is made to a module). FIG. 19 is a diagram showing an example of the state of the master in the DB server after a patch application process during a version upgrade (when a change is made to a module). FIG. 20 is a diagram showing an example of the state of folders in the AP server and the WEB server after patch application processing during a version upgrade (when changes are made to modules). FIG. 21 is a diagram showing an example of the master state in the DB server used in module synchronization processing during a version upgrade (when a change is made to a module). FIG. 22 is a diagram showing an example of the state of folders in the AP server and the WEB server after module synchronization processing during a version upgrade (when changes are made to the modules). FIG. 23 is a diagram showing an example of DB restoration when a later business system is introduced. FIG. 24 is a diagram showing an example of the state of the master in the DB server used in DB object synchronization processing when a later business system is introduced. FIG. 25 is a diagram showing an example of the state of the master in the DB server after DB object synchronization processing when a later business system is introduced. FIG. 26 is a diagram showing an example of the master state in the DB server used in module synchronization processing when a later business system is introduced. FIG. 27 is a diagram showing an example of the state of folders in an AP server after module synchronization processing when a later business system is introduced (when a synchronization target folder is set in the synchronization target folder setting file). FIG. 28 is a diagram showing an example of the state of folders in a web server after module synchronization processing when a later business system is introduced (when a synchronization target folder is set in the synchronization target folder setting file). FIG. 29 is a diagram showing an example of the state of folders in an AP server after module synchronization processing when a later business system is introduced (when no synchronization target folders are set in the synchronization target folder setting file). FIG. 30 is a diagram showing an example of the state of folders in a web server after module synchronization processing when a later business system is introduced (when no synchronization target folders are set in the synchronization target folder setting file).

Below, an embodiment of a synchronization control device, a synchronization control method, and a synchronization control program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the present embodiment.

[1. Overview]
(1) Terminology The terms used in this specification and drawings have the following meanings:
・DB objects: Objects such as tables, stored procedures, triggers, and views that are stored in a database.
・DB script: A file that describes operation commands to change, add, delete, etc. to DB objects. By including it in a patch and applying it, the changes, additions, and deletions are reflected.
Module: A file required to run an application. For example, an exe, dll, or js file.
・AP server: A server that deploys client-server application modules.
・WEB server: A server that deploys and publishes web application modules.
・DB server: A server on which a database management system exists.
· Business system: This is the unit for installing and managing each group of business applications that are installed in a component-based format.
- Common system: A management unit for functions and applications that are used in common by multiple business systems.

(2) Conventional technology and its problems
There are several types of ERP implementation, one of which is component-based ERP. The advantage of component-based ERP is that because management is separate for each system, it is possible to add and update the necessary version at the necessary time.

However, because management was separate, there was a disadvantage in that it was difficult to ensure consistency across the entire system. This disadvantage was particularly evident in events such as adding a new system later or upgrading each individual system.

(3) Outline and Effects of the Present Invention In this embodiment, for example, even if the system is divided into components, an area common to the system and an area for each component are managed separately. This concept makes it possible to detect inconsistencies and synchronize modules and DB objects commonly used by each system at the time of delivery, system startup, etc.

This makes it possible, for example, to prevent delivery staff responsible for each component from missing patches and ensure the quality of the entire system, enabling the provision of speedy, high-quality upgrades. In other words, it has become possible to provide a stable service that meets the requirements for version updates between business processes when operating business systems, as well as usage patterns such as step-by-step implementation and additional implementation for each business system. The specific configuration and operation are explained below.

2. Configuration
An example of the configuration of a synchronous control device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the synchronous control device 100.

The synchronous control device 100 is a commercially available desktop personal computer. Note that the synchronous control device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The synchronous control device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input/output interface unit 108. Each unit included in the synchronous control device 100 is connected to each other so that they can communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the synchronous control device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the synchronous control device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that data such as various masters described below may be stored in the server 200, for example.

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to provide a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like.

The storage unit 106 includes, for example, an applied patch version master 106a, a common system distribution module master 106b, a common system script synchronization management master 106c, a patch application history master 106d, an AP module master 106e, and a WEB module master 106f. The functions and contents of each master are described in detail in "(3) Master configuration" in [4. Processing overview, etc.] below.

The control unit 102 is a CPU or the like that performs overall control of the synchronous control device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs.

The control unit 102, functionally and conceptually, for example, comprises: (1) a DB restoration unit 102a; and (2) a DB object consistency check unit 102 as a DB object consistency check means for checking whether there exists a target business system to which the applied patch version identification information for the source business system has not been applied, among the applied patch version identification information consisting of information for identifying patch versions that have been applied in the past and the business systems to which the patch version was created or provided and was applied, by referring to a predetermined master, and, if there exists, specifying the target business system to which the applied patch version identification information for the source business system has not been applied as a target to which the applied patch version identification information for the source business system should be applied. b; (3) DB object synchronization unit 102c as DB object synchronization means for applying the applied patch version identification information for the source business system to the destination business system identified by the DB object consistency check means; (4) patch application unit 102d; (5) module consistency check unit 102e as module consistency check means for comparing the module master with the folder and checking whether there is a difference in file version or update date and time; and (6) module synchronization unit 102f as module synchronization means for downloading the contents of the module master to the folder when the module consistency check means checks that there is a difference.

The DB restoration unit 102a restores the DB.

The DB object consistency check unit 102b refers to predetermined masters (e.g., applied patch version master 106a, common system script synchronization management master 106c, and patch application history master 106d) to check whether there are any target business systems to which the patch version for the source business system has not been applied, and if there are any, identifies the target business systems to which the patch version for the source business system has not been applied as the target to which the patch version for the source business system should be applied.

Specifically, the DB object consistency check unit 102b performs the following processes (1) to (3).

(1) The DB object consistency check unit 102b first obtains the patch version for the source business system for which a flag indicating the need for synchronization (a flag set to "true") is set from the applied patch version master 106a, which includes the patch version for the source business system and a synchronization flag.

(2) The DB object consistency check unit 102b then obtains the target business system linked to the source business system that constitutes the patch version obtained in (1) from the common system script synchronization management master 106c, which includes the source business system and the target business system.

(3) Finally, if the patch version for the source business system obtained in (1) does not exist in the patch application history master 106d for the destination business system obtained in (2), the DB object consistency check unit 102b identifies the destination business system obtained in (2) as the target for application.

The DB object synchronization unit 102c applies the applied patch version for the source business system to the destination business system identified by the DB object consistency check unit 102b.

The patch application unit 102d applies the patch.

The module consistency check unit 102e compares the module masters (for example, the common system distribution module master 106b, the AP module master 106e, and the WEB module master 106f) with the folders to check whether there are differences in the file versions or update dates and times.

Specifically, the module consistency check unit 102e checks for the presence of a difference if there is no file in the folder, or if the module master and the folder are compared and the module names are the same but the file versions or file update dates and times are different.

More specifically, the module consistency check unit 102e compares the AP module master 106e and the WEB module master 106f with the folder, but in this case, if the same module name exists between the common system distribution module master 106b and the AP module master 106e and the WEB module master 106f, the comparison is made preferentially between the common system distribution module master 106b and the folder for modules identified by the same module name.

If the module consistency check unit 102e checks that there is a difference, the module synchronization unit 102f downloads the contents of the module master to the folder.

Specifically, the module synchronization unit 102f downloads the contents of the AP module master 106e and the WEB module master 106f to the folder, and in this case, if the same module name exists between the common system distribution module master 106b and the AP module master 106e and the WEB module master 106f, the module identified by the same module name is downloaded to the folder with the contents of the common system distribution module master 106f.

[3. Problems, Solutions, and Effects]
This section describes the problems, solutions, and effects of the present invention.

(1) Problems to be Solved by the Invention
There are several types of ERP implementation, one of which is component-based ERP. Component-based ERP has the advantage of being easy to integrate with existing business systems and allowing required functions to be added or removed as needed.

However, the disadvantage is that having multiple databases makes it difficult to manage module version control and the consistency of database objects.

In order to address the above disadvantages while enjoying the benefit of being able to use the required version when required, one can consider managing the system separately into separate areas and commonly managed areas. By taking this approach, when ensuring the consistency of the entire system, there is no need to consider the areas that need to be managed separately, and it is sufficient to focus on the commonly managed areas. However, there are the following challenges in automatically controlling the commonly managed areas while satisfying the following requirements:

The above demands included, for example, the following two points.
- Ensures consistency between commonly used modules and DB objects, even if the versions and timing of version upgrades of each business system are different.
- Ensure consistency between existing business systems and any business systems added later.

Regarding how to ensure consistency between the DB objects and local modules used in each business system, the following challenges A to D arose.
A. How to manage the separately controlled areas and the commonly controlled areas.
B. How to control synchronization.
C. When to synchronize.
D. How to detect an inconsistent environment.

As an example of inconsistencies, in the past, when a business system DB (accounting system DB) was added later, as shown in Figures 2 and 3, inconsistencies in the era name ("Reiwa" is not registered in the accounting system DB) and inconsistencies in the common system modules (the version is "1.0" in the accounting AP folder and accounting WEB folder) occurred between the human resources system DB and payroll system DB and the accounting system DB on the DB server, AP server, and WEB server, respectively.

(2) Solution of the Present Invention The solution used in the present invention is as shown in the table of Fig. 4. The table of Fig. 4 shows the management method, synchronization control method, synchronization timing, and inconsistent environment detection method for each module and DB object.

(3) Effects of the Invention In this embodiment, for example, it is possible to prevent delivery personnel responsible for each component from missing patches and ensure the quality of the entire system. As a result, for example, it is possible to provide speedy and high-quality version upgrades.

[4. Overview of Processing, etc.]
In this section, an overview of the processing according to this embodiment will be described.

(1) Objectives In this embodiment, the objective is to achieve the following 1 and 2 when a business system is introduced, upgraded, and started up.
1. Module synchronization 2. DB object synchronization

(2) System Configuration The system configuration in this embodiment will be described.

In this embodiment, the patch is made up of the following five folders.
・Common system script folder ・Common system module folder ・Business system script folder ・Business system AP module folder ・Business system WEB module folder

An example of a patch configuration in this embodiment is shown in Figure 5.

(3) Master Configuration In this section, the master configuration in this embodiment will be described with reference to FIGS.

The applied patch version master 106a is a master for managing the versions of all patches that have been applied so far. As shown in FIG. 6, the applied patch version master 106a includes, for example, applied patch version identification information (patch version) for identifying patch versions that have been applied in the past and consisting of the time when the patch version was created or provided and the business system to which it was applied, the business system, a synchronization flag, and the like. If the applied patch has a "common system script folder," as shown in FIG. 6, the "synchronization flag" becomes "true," which is a flag indicating the need for synchronization. Note that in the following explanation of the master, only records for the common system are shown for the sake of simplicity.

The common system distribution module master 106b is a master that stores common system modules. As shown in FIG. 7, the common system distribution module master 106b includes, for example, module identification data (module name), file version, module binary information, file update date and time, etc.

The common system script synchronization management master 106c is a master that specifies the synchronization source and synchronization destination of the "common script folder" and is a master necessary for controlling system dependencies. As shown in FIG. 8, the common system script synchronization management master 106c includes, for example, the source business system and the destination business system.

The patch application history master 106d is a master that manages the versions of patches applied to each business system DB. As shown in FIG. 9, the patch application history master 106d includes, for example, the applied patch version identification information (patch version), the business system, etc.

The AP module master 106e is a master that stores modules of the business system used in the AP server. As shown in FIG. 10, the AP module master 106e includes, for example, module identification data (module name), file version, deployment path, module binary information, file update date and time, etc. The deployment path is the path where the module is deployed when the module is downloaded from the master. The deployment path is determined from the folder structure of the patch.

The WEB module master 106f is a master that stores modules of the business system used by the WEB server. As shown in FIG. 11, the WEB module master 106f includes, for example, module identification data (module name), file version, deployment path, module binary information, file update date and time, etc. The explanation of the deployment path is the same as in the previous paragraph.

In the following description, there are a few points to note.
1. In the following explanation, the column names of "Module Binary Information" and "Business System" will be omitted.
2. In the following description, the common system distribution module master 106b, the AP module master 106e, and the WEB module master 106f may be collectively referred to as the "module masters."

(4) Processing Flow In this section, the processing flow in this embodiment will be described with reference to the flowchart in Fig. 12. In this section, the processing flow when the business system is introduced for the first time or when a subsequent business system is introduced will be described in (4-1) below, the processing flow when upgrading will be described in (4-2) below, and the processing flow when the system is started will be described in (4-3) below.

(4-1) When a Business System is First Introduction or a Business System is Later Introduction First, the processing timing is determined (step S1 in FIG. 12). In this item, it is determined that the processing timing is when a business system is first introduced or when a business system is later introduced.

Next, the DB restoration unit 102a performs DB restoration (step S2 in FIG. 12).

Next, the DB object consistency check unit 102b performs a consistency check on the DB object (step S3 in FIG. 12).

If an inconsistency exists (NG in step S3 in FIG. 12), the DB object synchronization unit 102c performs a synchronization process for the DB objects (step S4 in FIG. 12).

On the other hand, if no inconsistency exists (OK in step S3 in FIG. 12), the patch application unit 102d performs the patch application process (step S5 in FIG. 12).

Next, the module consistency check unit 102e performs a consistency check on the module (step S6 in FIG. 12).

If an inconsistency exists (NG in step S6 in FIG. 12), the module synchronization unit 102f performs module synchronization processing (step S7 in FIG. 12).

On the other hand, if no inconsistency exists (OK in step S6 in FIG. 12), the process ends (End in FIG. 12).

(4-2) When Upgrading First, the processing timing is determined (step S1 in FIG. 12). In this item, it is determined that the processing timing is when upgrading.

Next, the DB object consistency check unit 102b performs a consistency check on the DB object (step S3 in FIG. 12).

The process from this point on is the same as (4-1), so we will not explain it here.

(4-3) At System Start-Up First, the processing timing is determined (step S1 in FIG. 12). In this item, it is assumed that the processing timing is at system start-up.

Next, the DB object consistency check unit 102b performs a consistency check on the DB object (step S8 in FIG. 12).

If an inconsistency exists (NG in step S8 in FIG. 12), an error is displayed (step S9 in FIG. 12) and the process ends (END in FIG. 12).

On the other hand, if no inconsistency exists (OK in step S8 of FIG. 12), the module consistency check unit 102e performs a consistency check of the module (step S6 of FIG. 12).

The process from this point on is the same as (4-1), so we will not explain it here.

(5) Overview of Processing In this section, an overview of the processing in this embodiment will be described.

(5-1) DB restoration process
The DB restoration unit 102a selects and restores a DB to be introduced from a set of system DBs in which all business systems and the integrated patch management DB have been backed up.

(5-2) DB object consistency check process
The DB object consistency check unit 102b refers to the common system script synchronization management master 106c, and compares the patch application history master 106d and applied patch version master 106a of each business system DB for all DBs of the destination business system whose source business system is the "common system" to check whether there are any patches that have not been applied. Specifically, the check is performed in the following steps 1 to 3.

1. First, the DB object consistency check unit 102b extracts rows whose synchronization flag is true from the applied patch version master 106a (i.e., obtains a list of patches that require synchronization).

2. Next, the DB object consistency check unit 102b obtains a list of target business systems by extracting rows where the "Business System" in the applied patch version master 106a matches the "Source Business System" in the common system script synchronization management master 106c for each row extracted in 1.

3. Finally, for each row extracted in 2., the DB object consistency check unit 102b refers to the patch application history master 106d for the business specified in the "target business system" of the common system script synchronization management master 106c, and checks whether there is a history that matches the "patch version" in the row extracted from the applied patch version master 106a in 1. (i.e., performs a patch application check). If there is a matching history, the DB object consistency check unit 102b determines that there is no difference (no missed application), and conversely, if there is no matching history, it determines that there is a difference (missed application).

(5-3) DB object synchronization processing
The DB object synchronization unit 102c obtains a list of business systems and patches for which patch omissions have been discovered from the results of the DB object consistency check in (5-2).The DB object synchronization unit 102c then applies the scripts in the common system script folder to the business systems for which patch omissions have been discovered.

(5-4) Patch Application Process The patch application unit 102d executes the following processes 1 to 7 in order.

1. The patch application unit 102d stores the modules in the common system module folder in the common system distribution module master 106b of the integrated patch management DB.

2. The patch application unit 102d stores the modules in the business system AP module folder in the AP module master 106e of the business system DB.

3. The patch application unit 102d stores the modules under the business system web module folder in the web module master 106f of the business system DB.

4. If there is a DB script under the common system script folder, the patch application unit 102d refers to the common system script synchronization management master 106c and applies the contents of the common system script folder to all DBs of the target business system where the source business system is the "common system."

5. The patch application unit 102d applies the DB scripts in the business system script folder to the business system DB.

6. The patch application unit 102d updates the applied patch version master 106a in the integrated patch management DB. At this time, if there is a "common system script folder", the patch application unit 102d sets the "synchronization flag" to true.

7. The patch application unit 102d updates the patch application history master 106d in the business system DB.

(5-5) Module Consistency Check Processing The module consistency check unit 102e compares the module master with the local folder, and checks whether there are any problems with the file version, update date and time, etc. Specifically, the following checks are performed on the following targets:

The modules to be checked are 1 or 2 below.
1. A module that does not exist in the common system distribution module master 106b and exists only in the AP module master 106e and the WEB module master 106f. 2. A module that exists in common between the common system distribution module master 106b and the AP module master 106e and the WEB module master 106f.

When the module to be checked is 1., the module consistency checking unit 102e checks the paths specified in the "placement paths" of the AP module master 106e and the WEB module master 106f to see if they fall under A or B below. On the other hand, when the module to be checked is 2., the module consistency checking unit 102e checks the paths specified in the "placement paths" of the AP module master 106e and the WEB module master 106f for files placed on the paths specified in the "files with folders set to be synchronized" to see if they fall under A or B below.
A. The file does not exist in the local folder.
B. There is a difference in the file version or file update date and time.

The module consistency check unit 102e determines that there is a difference if the result corresponds to A or B, and determines that there is no difference otherwise (if the result corresponds to neither A nor B).

When determining whether or not a module falls under "B," the module consistency check unit 102e compares the AP module master 106e and the WEB module master 106f with the folder. In this case, if the same module name exists between the common system distribution module master 106b and the AP module master 106e and the WEB module master 106f, the module identified by the same module name is compared preferentially with the common system distribution module master 106b and the folder.

(5-6) Module Synchronization Processing The module synchronization unit 102f downloads the modules stored in the AP module master 106e and the WEB module master 106f to the path specified by the "arrangement path." At this time, if the same module exists between the AP module master 106e and the WEB module master 106f and the common system distribution module master 106b, the module synchronization unit 102f preferentially downloads the module in the common system distribution module master 106b.

5. Specific Examples of Processing
This section describes specific examples of processing according to this embodiment. In this section, the processing at the time of initial business system installation is described below in [5-1], the processing at the time of version upgrade (when changes are made to DB objects) is described below in [5-2], the processing at the time of version upgrade (when changes are made to modules) is described below in [5-3], the processing at the time of subsequent business system installation is described below in [5-4], and the processing at system startup is described below in [5-5].

[5-1. When introducing the business system for the first time]
In this section, the process at the time of initial introduction of the business system will be described using FIGS. 13 to 15 while referring to the flowchart in FIG.

(1) Database recovery
The DB restoration unit 102a restores a template DB in the DB server when each business system is added (step S2 in FIG. 12). In this example, as shown in FIG. 13, a situation is considered in which an integrated patch management DB, a personnel system DB, and a payroll system DB are restored.

(2) DB Object Consistency Check When restoring from a set of system DBs of the same version, no difference in DB objects occurs, so the DB object consistency check unit 102b determines that no inconsistency exists (Step S3 in FIG. 12: OK).

(3) DB object synchronization processing
Since the result of the DB object consistency check is OK (no inconsistency exists), the DB object synchronization process is not performed.

(4) Module consistency check
Immediately after restoring the DB, there are no modules on the AP server and the WEB server, so this corresponds to "A. No file exists in the local folder" in (5-5) of [4. Overview of processing, etc.]. Therefore, the module consistency check unit 102e determines that there is an inconsistency (step S6 in FIG. 12: NG).

(5) Module Synchronization Processing Since the module consistency check is NG (because there is an inconsistency), the module synchronization unit 102f performs module synchronization processing (step S7 in FIG. 12). Specifically, the module synchronization unit 102f downloads the contents of the AP module master 106e and the WEB module master 106f shown in FIG. 14 to the AP server and the WEB server, and at this time, performs synchronization control for files set as synchronization target folders, taking into account the common system distribution module master 106b (if there is a system that you do not want to synchronize, you can remove it from the synchronization target folder). In this example, as shown in Fig. 14, four folders, namely, Personnel AP Folder\Bin, Payroll AP Folder\Bin, Personnel WEB Folder\Bin, and Payroll WEB Folder\Bin, are set as folders to be synchronized, so that when the same module name exists between the common system distribution module master 106b and the AP module master 106e and WEB module master 106f, the module synchronization unit 102f downloads the contents of the common system distribution module master 106b to the four folders for modules identified by the same module name. As a result, the contents of the Personnel AP Folder\Bin and Payroll AP Folder\Bin in the AP server and the Personnel WEB Folder\Bin and Payroll WEB Folder\Bin in the WEB server are updated as shown in Fig. 15.

Since the module synchronization process results in a successful module consistency check (OK in step S6 of FIG. 12), the process for this item ends (End of FIG. 12).

[5-2. When upgrading (when changes are made to DB objects)]
In this section, the process of upgrading (when changes are made to DB objects) will be explained using Figures 16 and 17 while referring to the flowchart in Figure 12. Note that this section assumes an environment after the completion of all steps in [5-1. Initial business system installation].

(1) DB object consistency check
It is assumed that the result of the DB object consistency check is OK (OK in step S3 in FIG. 12).

(2) DB object synchronization processing
Since the result of the DB object consistency check is OK (no inconsistency exists), the DB object synchronization process is not performed.

(3) Patch Application Processing The patch application unit 102d applies the patch shown in Fig. 16 (step S5 in Fig. 12). Specifically, the patch application unit 102d performs the following processes 1 to 3.

1. Referring to FIG. 16, since there is a DB script under the common system script folder, the patch application unit 102d refers to the common system script synchronization management master 106c and applies the contents of the common system script folder to all DBs in the target business system where the source business system is the "common system."

2. The patch application unit 102d updates the applied patch version master 106a in the integrated patch management DB. At this time, since the "common system script folder" exists, the patch application unit 102d sets the "synchronization flag" to true. The updated applied patch version master 106a is shown in FIG. 17.

3. The patch application unit 102d updates the patch application history master 106d in the business system DB. The updated patch application history master 106d is shown in FIG. 17.

In addition, the following two states are the same as the environment after the completion of all steps in [5-1. Initial business system implementation], so we will omit the description.
- DB server module master - AP server and WEB server status

(4) Module Consistency Check It is assumed that the result of the module consistency check is OK (OK in step S6 of FIG. 12).

(5) Module Synchronization Processing Since the result of the module consistency check is OK (no inconsistency is present), the module synchronization processing is not performed. This ends the processing in this item (end of FIG. 12).

[5-3. When upgrading (when changes are made to the module)]
In this section, the process of upgrading (when a change is made to a module) will be explained using Figures 18 to 22 while referring to the flowchart in Figure 12. Note that this section assumes an environment after the completion of all steps in [5-2. When upgrading (when a change is made to a DB object)].

(1) DB object consistency check
It is assumed that the result of the DB object consistency check is OK (OK in step S3 in FIG. 12).

(2) DB object synchronization processing
Since the result of the DB object consistency check is OK (no inconsistency exists), the DB object synchronization process is not performed.

(3) Patch Application Processing The patch application unit 102d applies the patch shown in Fig. 18 (step S5 in Fig. 12). Specifically, the patch application unit 102d performs the following processes 1 to 4 for the personnel system, and the following processes 1 to 2 for the common system.

(3-1) Regarding the Personnel System 1. The patch application unit 102d stores the modules in the business system AP module folder and below in the AP module master 106e of the personnel system DB. The AP module master 106e (personnel system) after storage is shown in FIG.

2. The patch application unit 102d stores the modules in the business system web module folder in the web module master 106f of the personnel system DB. The web module master 106f (personnel system) after storage is shown in Figure 19.

3. The patch application unit 102d updates the applied patch version master 106a in the integrated patch management DB. Note that in FIG. 19, the patch application history of the business system is omitted for ease of explanation.

4. The patch application unit 102d updates the patch application history master 106d in the personnel system DB. The updated patch application history master 106d is shown in FIG. 19.

(3-2) Regarding the common system 1. The patch application unit 102d stores the modules in the common system module folder in the common system distribution module master 106b of the integrated patch management DB. The common system distribution module master 106b after storage is shown in FIG.

2. The patch application unit 102d updates the applied patch version master 106a in the integrated patch management DB. The updated applied patch version master 106a is shown in FIG. 19.

Note that the following state is the same as the environment after completing all steps in [5-2. When upgrading (when changes are made to DB objects)], so we will omit the description here.
· Status of the common system script synchronization management master 106c and era name master of the DB server

(4) Module Integrity Check Immediately after applying a patch, an inconsistency occurs between the module master of the DB server and the local folders of the AP server and the WEB server (NG in step S6 in FIG. 12). Specifically, FIG. 20 shows the state of the folders in the AP server and the WEB server after the patch application process at the time of version upgrade (when a change is made to a module), but the contents of FIG. 20 are the same as FIG. 15 which shows the state of the AP server and the WEB server after "(5) Module Synchronization Process" in [5-1. Initial Business System Installation]. Comparing the module master of the DB server in FIG. 19 updated in this section [5-3] with the local folders of the AP server and the WEB server in FIG. 20 which have not yet been updated in this section [5-3], the part enclosed by hatching in FIG. 20 is different from [4. Since this corresponds to "There is a difference in the version or file update date and time of B file" in (5-5) of "Overview of Processing, etc.", this is the location of the inconsistency (note that, as shown in FIG. 19, since there are three modules with the same module name, "common system A.exe", "common system B.dll", and "common system AA.dll", between the common system distribution module master 106b and the AP module master 106e and the WEB module master 106f, the module consistency checking unit 102e gives priority to comparing the common system distribution module master 106b and the folder for these three modules). Therefore, the module consistency checking unit 102e determines that an inconsistency exists (NG in step S6 of FIG. 12).

(5) Module Synchronization Processing Since the module consistency check is NG (because there is an inconsistency), the module synchronization unit 102f performs module synchronization processing in accordance with the following rules 1 and 2 (step S7 in FIG. 12).
Rule 1. The module synchronization unit 102f downloads the modules stored in the AP module master 106e and the WEB module master 106f to the path specified by the "distribution path."
Rule 2: At this time, if the same module exists in the AP module master 106e and the WEB module master 106f and in the common system distribution module master 106b, the module synchronization unit 102f downloads the module in the common system distribution module master 106b with priority.
Note that the following items are not subject to the module consistency check, so their description will be omitted.
· Status of the common system script synchronization management master 106c and era name master of the DB server

Specifically, the module synchronization unit 102f downloads the contents of the AP module master 106e and the WEB module master 106f shown in FIG. 21 to the AP server and the WEB server, but at this time, for files set as folders to be synchronized, it performs synchronization control taking into account the common system distribution module master 106b as well (if there is a system that you do not want to synchronize, you can remove it from the folders to be synchronized). In this example, as shown in FIG. 21, four folders, namely, HR AP folder\Bin, Payroll AP folder\Bin, HR WEB folder\Bin, and Payroll WEB folder\Bin, are set as folders to be synchronized. Therefore, if the same module name exists between the common system distribution module master 106b and the AP module master 106e and the WEB module master 106f, the module synchronization unit 102f downloads the contents of the common system distribution module master 106b to the four folders for modules identified by the same module name.

In other words, the module synchronization unit 102f basically downloads the contents of the AP module master 106e and the WEB module master 106f shown in FIG. 21 to the AP server and the WEB server in accordance with rule 1. However, taking rule 2 into consideration, the three modules "common system A.exe", "common system B.dll", and "common system AA.dll" exist in common between the AP module master 106e and the WEB module master 106f and the common system distribution module master 106b, so the module synchronization unit 102f preferentially downloads the module (file version: 1.3) in the common system distribution module master 106b in FIG. 21.

By performing the above processing, the contents of the HR AP Folder\Bin and Payroll AP Folder\Bin on the AP server and the HR WEB Folder\Bin and Payroll WEB Folder\Bin on the WEB server are updated as shown in Figure 22.

The module synchronization process results in a successful module consistency check (OK in step S6 of FIG. 12), and the process ends (End of FIG. 12).

[5-4. When introducing a new business system]
In this section, the process of introducing a new business system will be explained using Figures 23 to 30 while referring to the flowchart in Figure 12. Note that this section assumes an environment after the completion of all steps in [5-3. When upgrading (when changes are made to modules)].

(1) Database recovery
The DB restoration unit 102a restores the accounting system DB in the DB server, as shown in FIG. 23 (step S2 in FIG. 12).

(2) DB object consistency check
The DB object consistency check unit 102b checks the consistency of the DB object in the following order 1 to 3 (step S3 in FIG. 12).

1. The DB object consistency check unit 102b extracts rows where the "synchronization flag" is true from the applied patch version master 106a in FIG. 24 (i.e., obtains a list of patches that require synchronization). As a result, the DB object consistency check unit 102b extracts "20200115.Common System".

2. The DB object consistency check unit 102b obtains a list of target business systems by extracting columns that match the "Business System" in the applied patch version master 106a in FIG. 24 and the "Source Business System" in the common system script synchronization management master 106c in FIG. 24. As a result, the DB object consistency check unit 102b extracts the personnel system, payroll system, and accounting system.

3. The DB object consistency check unit 102b refers to the patch application history master 106d in FIG. 24 for the business specified in the "Applied business system" in the common system script synchronization management master 106c in FIG. 24, and checks whether there is a history that matches the "patch version" in the applied patch version master 106a in FIG. 24 described in 1. (i.e., checks patch application). As a result, the DB object consistency check unit 102b determines that the consistency check is OK because the personnel system has a history of "20200115.common system", and also determines that the consistency check is OK because the payroll system has a history of "20200115.common system". In contrast, the DB object consistency check unit 102b determines that the consistency check is NG because the accounting system does not have a history of "20200115.common system".

Note that the following items are not subject to DB object consistency checking, so we will omit their description here.
- DB server module master status - AP server and WEB server status

(3) DB object synchronization processing
The DB object synchronization unit 102c performs DB object synchronization processing to apply the "20200115.Common System" patch to the accounting system, as shown in Fig. 25 (step S4 in Fig. 12). As a result of the DB object synchronization processing, the result of the DB object consistency check becomes OK (OK in step S3 in Fig. 12).

(4) Module consistency check Immediately after the accounting system DB is restored, there are no accounting system modules on the AP server or WEB server, so this corresponds to "A. No file exists in the local folder" in (5-5) of [4. Overview of processing, etc.]. For this reason, the module consistency check unit 102e determines that an inconsistency exists (step S6: NG in FIG. 12).

(5) Module Synchronization Processing Since the module consistency check is NG (because there is an inconsistency), the module synchronization unit 102f performs module synchronization processing in accordance with the following rules 1 and 2 (step S7 in FIG. 12).
Rule 1. The module synchronization unit 102f downloads the modules stored in the AP module master 106e and the WEB module master 106f to the path specified by the "distribution path."
Rule 2: At this time, if the same module exists in the AP module master 106e and the WEB module master 106f and in the common system distribution module master 106b, the module synchronization unit 102f downloads the module in the common system distribution module master 106b with priority.
Note that the following items are not subject to the module consistency check, so their description will be omitted.
· Status of the common system script synchronization management master 106c and era name master of the DB server

Below, we will explain the cases when the synchronized folder in the synchronized folder setting file is set and when it is not.

(5-1) When a synchronization target folder is set When a synchronization target folder is set in the synchronization target folder setting file, the module synchronization unit 102f downloads the contents of the AP module master 106e and the WEB module master 106f shown in Fig. 26 to the AP server and the WEB server, but at this time, for the file set as the synchronization target folder, synchronization control is performed taking into consideration the common system distribution module master 106b as well (if there is a system that you do not want to synchronize, you can remove it from the synchronization target folder). In this example, as shown in Fig. 26, six folders, namely, personnel AP folder\Bin, payroll AP folder\Bin, accounting AP folder\Bin, personnel WEB folder\Bin, payroll WEB folder\Bin, and accounting WEB folder\Bin, are set as synchronization target folders, so when the same module name exists between the common system distribution module master 106b and the AP module master 106e and the WEB module master 106f, the module synchronization unit 102f downloads the contents of the common system distribution module master 106b to the six folders for modules identified by the same module name.

In other words, the module synchronization unit 102f basically follows rule 1 and downloads the contents of the AP module master 106e and WEB module master 106f shown in FIG. 26 to the AP server and WEB server. However, taking rule 2 into consideration, the three modules "common system A.exe", "common system B.dll", and "common system AA.dll" exist in common between the AP module master 106e and WEB module master 106f and the common system distribution module master 106b, so the module synchronization unit 102f preferentially downloads the module (file version: 1.3) in the common system distribution module master 106b in FIG. 26.

By the above processing, the HR AP Folder\Bin, Payroll AP Folder\Bin, and Accounting AP Folder\Bin on the AP server are updated as shown in Figure 27, and the HR WEB Folder\Bin, Payroll WEB Folder\Bin, and Accounting WEB Folder\Bin on the WEB server are updated as shown in Figure 28.

As shown in FIG. 27, on the AP server, there is consistency between the HR AP folder\Bin and the Payroll AP folder\Bin, and the Accounting AP folder\Bin. Also, as shown in FIG. 28, on the WEB server, there is consistency between the HR WEB folder\Bin and the Payroll WEB folder\Bin, and the Accounting WEB folder\Bin.

As explained above in section (5-1), when a synchronization target folder is set in the synchronization target folder setting file, the modules present in the common system distribution module master 106b are given priority, and the entire system is synchronized as shown in Figures 27 and 28.

The module synchronization process results in a successful module consistency check (OK in step S6 of FIG. 12), and the process ends (End of FIG. 12).

(5-2) When a synchronization target folder is not set When a synchronization target folder is not set in the synchronization target folder setting file, the module synchronization unit 102f downloads the contents of the AP module master 106e and the WEB module master 106f shown in Fig. 26 to the AP server and the WEB server. As a result, the personnel AP folder\Bin, payroll AP folder\Bin, and accounting AP folder\Bin in the AP server are updated as shown in Fig. 29, and the personnel WEB folder\Bin, payroll WEB folder\Bin, and accounting WEB folder\Bin in the WEB server are updated as shown in Fig. 30.

As shown in Figure 29, in the AP server, an inconsistency has occurred between the Personnel AP Folder\Bin and Payroll AP Folder\Bin, and the Accounting AP Folder\Bin. Also, as shown in Figure 30, in the WEB server, an inconsistency has occurred between the Personnel WEB Folder\Bin and Payroll WEB Folder\Bin, and the Accounting WEB Folder\Bin.

As explained above in section (5-2), if the synchronization target folder is not set in the synchronization target folder setting file, different versions of the common system module will be obtained for each business system, resulting in system inconsistencies, as shown in Figures 29 and 30.

[5-5. Processing at system startup]
In this section, the process at system startup will be described with reference to the flowchart in FIG.

(1) DB object consistency check Since this involves a system stop, automatic synchronization is not assumed, but the DB object consistency check unit 102b may be made to automatically check the consistency of DB objects as necessary. For example, if the consistency check is NG due to a human error or the like (NG in step S8 of FIG. 12), for example, the following error is displayed.
Error: "The following patches have not been applied to the XX system. Please apply the patches and update your system. (A list of patches that have not been applied will be displayed.)"

(2) Module Integrity Check On the other hand, if the result of the DB object integrity check is OK (OK in step S8 in FIG. 12), the module integrity check unit 102e performs a module integrity check. If the module integrity check is forgotten after the patch application process due to a work mistake at the time of delivery, the result of the module integrity check may be NG (NG in step S6 in FIG. 12).

(3) Module Synchronization Processing If the result of the module consistency check is NG, the module synchronization unit 102f performs module synchronization processing in a manner similar to “(5) Module Synchronization Processing” in [5-3. Processing at the time of version upgrade (when changes are made to a module)] (step S7 in FIG. 12).

The module synchronization process results in a successful module consistency check (OK in step S6 of FIG. 12), so the process for this item ends (End of FIG. 12).

[6. Summary of the present embodiment]
In this way, according to the synchronous control device 100 of this embodiment, it is possible to enjoy the advantage of being able to separate management for each system, while eliminating the disadvantage that it is difficult to ensure consistency across the entire system.

[7. Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

8. Other embodiments
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including search conditions and other parameters, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the synchronous control device 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the synchronous control device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the synchronous control device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the synchronous control device 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a Blu-ray (registered trademark) Disc, and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

The synchronous control device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The synchronous control device 100 may also be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is useful in all industries and business sectors.

100 Synchronous control device 102 Control unit
102a DB restoration unit
102b DB object consistency check unit
102c DB object synchronization unit
102d Patch application unit
102e Module consistency check unit
102f module synchronization unit 104 communication interface unit 106 storage unit
106a Applied patch version master
106b Common system distribution module master
106c Common system script synchronization management master
106d Patch application history master
106e AP module master
106f WEB module master 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (7)

A synchronous control device including a control unit,
The control unit is
a DB object consistency check means for checking, by referring to a predetermined master, whether or not there exists a target business system to which the applied patch version identification information for a source business system has not been applied, among applied patch version identification information for identifying patch versions that have been applied in the past, the applied patch version identification information being composed of information for identifying the business systems to which the patch version was created or provided and the patch version was applied, and, if there exists such a target business system, specifying the target business system to which the applied patch version identification information for the source business system has not been applied as a target to which the applied patch version identification information for the source business system should be applied;
a DB object synchronization means for applying the applied patch version identification information of the source business system to the destination business system identified by the DB object consistency check means;
a module consistency check means for comparing a module master with a folder and checking whether there is a difference in file version or update date and time;
a module synchronization means for downloading the contents of the module master to the folder when the module consistency check means checks that there is a difference;
To have
A synchronous control device comprising: The predetermined master is
an applied patch version master including the applied patch version identification information and a synchronization flag for the source business system;
a common system script synchronization management master including the source business system and the destination business system;
a patch application history master prepared for each of the application destination business systems, the patch application history master including the applied patch version identification information for the application destination business systems;
It is composed of
The DB object consistency check means includes:
obtaining, from the applied patch version master, the applied patch version identification information for the source business system for which a flag indicating the need for synchronization is set;
obtain, from the common system script synchronization management master, a target business system associated with the source business system constituting the obtained applied patch version identification information;
identifying the acquired destination business system as the application target when the applied patch version identification information for the acquired source business system does not exist in the patch application history master for the acquired destination business system;
The synchronous control device according to claim 1 . The module master includes module identification data, a file version, and a file update date and time;
The folder includes module identification data, a file version, and a file update date and time;
The module consistency check means includes:
If there is no file in the folder, or if the module master and the folder are compared and the module identification data are the same but the file version or the file update date and time is different, checking that there is a difference;
3. A synchronous control device according to claim 1 or 2. The module master:
a common system distribution module master including module identification data, file version, and file update date and time, the common system distribution module master storing modules of the common system;
an AP module master including module identification data, file version, and file update date and time, storing modules of a business system used in an AP server;
a WEB module master including module identification data, file version, and file update date and time, storing modules of a business system used in a WEB server;
It is composed of
The module consistency check means includes:
comparing the AP module master and the WEB module master with the folder, and in this case, if identical module identification data exists between the common system distribution module master and the AP module master and the WEB module master, comparing the common system distribution module master with the folder with priority for modules identified by the identical module identification data;
4. The synchronous control device according to claim 3 . The module master:
a common system distribution module master including module identification data, file version, and file update date and time, the common system distribution module master storing modules of the common system;
an AP module master including module identification data, file version, and file update date and time, which stores modules of a business system used in an AP server;
a WEB module master including module identification data, file version, and file update date and time, storing modules of a business system used by a WEB server;
It is composed of
The module synchronization means includes:
downloading the contents of the AP module master and the WEB module master into the folder, and at this time, if identical module identification data exists between the common system distribution module master and the AP module master and the WEB module master, downloading the contents of the common system distribution module master into the folder for modules identified by the identical module identification data;
5. A synchronous control device according to claim 1, wherein: A synchronization control method executed in an information processing device including a control unit,
Executed by the control unit,
a DB object consistency check step of checking, with reference to a predetermined master, whether or not there exists a target business system to which the applied patch version identification information for a source business system has not been applied, among applied patch version identification information for identifying patch versions that have been applied in the past, the applied patch version identification information being composed of information for identifying the business systems to which the patch version was created or provided and was applied, and, if there exists such a target business system, identifying the target business system to which the applied patch version identification information for the source business system has not been applied as a target to which the applied patch version identification information for the source business system should be applied;
a DB object synchronization step of applying the applied patch version identification information of the source business system to the destination business system identified in the DB object consistency check step;
A module consistency check step for comparing the module master with the folder to check whether there is a difference in file version or update date and time;
a module synchronization step of downloading the contents of the module master to the folder when it is determined that there is a difference in the module consistency check step;
containing,
A synchronization control method comprising: A synchronization control program to be executed by an information processing device having a control unit,
To cause the control unit to execute
a DB object consistency check step of checking, with reference to a predetermined master, whether or not there exists a target business system to which the applied patch version identification information for a source business system has not been applied, among applied patch version identification information for identifying patch versions that have been applied in the past, the applied patch version identification information being composed of information for identifying the business systems to which the patch version was created or provided and was applied, and, if there exists such a target business system, identifying the target business system to which the applied patch version identification information for the source business system has not been applied as a target to which the applied patch version identification information for the source business system should be applied;
a DB object synchronization step of applying the applied patch version identification information of the source business system to the destination business system identified in the DB object consistency check step;
A module consistency check step for comparing the module master with the folder to check whether there is a difference in file version or update date and time;
a module synchronization step of downloading the contents of the module master to the folder when it is determined that there is a difference in the module consistency check step;
containing,
A synchronous control program comprising:

Images