Synchronization control device, synchronization control method, and synchronization control program
The synchronous control device addresses the challenge of maintaining consistency in component-based ERP systems by managing patch versions and module synchronization, ensuring high-quality and efficient system updates.
Patent Information
- Application Number
- JP2021167378
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-02-26
- Filing Date
- 2021-10-12
- Publication Date
- 2024-11-07
- Estimated Expiration
- 2041-10-12
AI Technical Summary
Component-based ERP systems face challenges in ensuring consistency across multiple business systems due to separate management, making it difficult to maintain synchronization during system additions or upgrades.
A synchronous control device and method that utilizes a control section to manage patch version identification, DB object consistency check, and module synchronization to ensure consistency across business systems by comparing and synchronizing patch versions and module files.
Ensures consistency across business systems while allowing separate management, enabling high-quality and efficient version updates and preventing inconsistencies during system deliveries.
Smart Images

Figure 0007579229000001 
Figure 0007579229000002 
Figure 0007579229000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a synchronization control device, a synchronization control method, and a synchronization control program. [Background technology]
[0002] Patent document 1 discloses a server device, an information processing method, and a program that can prompt server application upgrades even in a configuration in which application upgrades on the server and client are not performed simultaneously in a data synchronization system (see paragraphs 0001 and 0035 of Patent document 1, etc.). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2018-45307 A Summary of the Invention [Problem to be solved by the invention]
[0004] There are several types of ERP (Enterprise Resources Planning) implementation forms, 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.
[0005] On the other hand, because management is separate, there is a disadvantage that it is difficult to guarantee the consistency of 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 above describes synchronization control by upgrading, the method of synchronization control is limited to upgrading the server application.
[0006] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a synchronization control device, a synchronization control method, and a synchronization control program that can enjoy the advantage of being able to separate management for each system while eliminating the disadvantage of it being difficult to ensure consistency across the entire system. [Means for solving the problem]
[0007] In order to solve the above-mentioned problems and achieve the object, a synchronization control device according to the present invention is a synchronization control device having a control unit, the control unit referring to a predetermined master, checking whether there is a destination 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 that 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 the patch version was applied, and if there is, specifying the destination 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, DB object consistency check means for applying the applied patch version identification information for the source business system to the destination business system specified by the DB object consistency check means, 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, and module synchronization means for downloading the contents of the module master to the folder if the module consistency check means checks that there is a difference.
[0008] In addition, in the synchronization control device of the present invention, the specified 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 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, acquires from the common system script synchronization management master a destination business system linked to the source business system constituting the acquired applied patch version identification information, and if the applied patch version identification information for the acquired source business system is not present in the patch application history master for the acquired destination business system, identifies the acquired destination business system as the target to be applied.
[0009] In addition, in the synchronization control device of 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 if there is no file in the folder, or if 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.
[0010] In addition, in the synchronization control device of 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, if the same module identification data exists between the common system distribution module master, the AP module master, and the WEB module master, for modules identified by the same module identification data, the comparison is made preferentially between the common system distribution module master and the folder.
[0011] In addition, in the synchronization control device of 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, 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.
[0012] Furthermore, a synchronization control method according to the present invention is a synchronization control method executed by an information processing device having a control unit, the synchronization control method including: a DB object consistency check step of checking, by referring to a predetermined master executed by the control unit, whether or not there exists a destination 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 at the time of creation or provision of the patch version and the business systems to which the patch version was applied, and, if there exists, identifying the destination 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 for the source business system to the destination business system identified in the DB object consistency check step; a module consistency check step of comparing a module master with a folder to check whether or not there is a difference in file version or update date and time; and a module synchronization step of 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.
[0013] Furthermore, a 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, the synchronization control program being characterized in that it includes: a DB object consistency check step of checking, by referring to a predetermined master, whether or not there exists a destination 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, which is information for identifying patch versions that have been applied in the past and is composed of business systems at the time of creation or provision of the patch version and the target of the application, and, if there exists, identifying the destination 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 for the source business system to the destination business system identified in the DB object consistency check step; a module consistency check step of comparing a module master with a folder to check whether or not there is a difference in file version or update date and time; and a module synchronization step of 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. Effect of the Invention
[0014] According to the present invention, it is possible to obtain 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. [Brief description of the drawings]
[0015] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a synchronization control device. [Diagram 2] 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. [Diagram 3]FIG. 3 is a diagram showing an example of an occurrence of inconsistency in the AP server and the WEB server between the personnel system DB and the payroll system DB, and the accounting system DB. [Figure 4] 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. [Diagram 5] FIG. 5 is a diagram illustrating an example of a patch configuration. [Figure 6] FIG. 6 is a diagram illustrating an example of the applied patch version master. [Figure 7] FIG. 7 is a diagram illustrating an example of the common system distribution module master. [Figure 8] FIG. 8 is a diagram illustrating an example of the common system script synchronization management master. [Figure 9] FIG. 9 is a diagram illustrating an example of the patch application history master. [Figure 10] FIG. 10 illustrates an example of the AP module master. [Figure 11] FIG. 11 is a diagram illustrating an example of the WEB module master. [Figure 12] FIG. 12 is a diagram showing an example of a flowchart of processing in this embodiment. [Figure 13] FIG. 13 is a diagram showing an example of DB restoration when a business system is first introduced. [Figure 14] FIG. 14 is a diagram showing an example of a master state in a DB server used in module synchronization processing when a business system is first introduced. [Figure 15] 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. [Figure 16] 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). [Figure 17]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 a DB object). [Figure 18] 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). [Figure 19] FIG. 19 is a diagram showing an example of the state of the master in the DB server after a patch application process at the time of version upgrade (when a change is made to a module). [Figure 20] 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). [Figure 21] FIG. 21 is a diagram showing an example of the state of the master in the DB server used in module synchronization processing during a version upgrade (when a change is made to a module). [Figure 22] 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 a change is made to a module). [Figure 23] FIG. 23 is a diagram showing an example of DB restoration when a later business system is introduced. [Figure 24] FIG. 24 is a diagram showing an example of a master state in a DB server used in DB object synchronization processing when a later business system is introduced. [Diagram 25] FIG. 25 is a diagram showing an example of a master state in a DB server after DB object synchronization processing when a later business system is introduced. [Figure 26] FIG. 26 is a diagram showing an example of a master state in a DB server used in module synchronization processing when a later business system is introduced. [Figure 27] 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). [Figure 28] 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). [Figure 29] 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 folder is set in the synchronization target folder setting file). [Diagram 30] 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). DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0016] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of a synchronous control device, a synchronous control method, and a synchronous control program according to the present invention will be described in detail with reference to the accompanying drawings. Note that the present invention is not limited to the preferred embodiments.
[0017] [1. Overview] (1) Terminology The terms used in the present specification and drawings have the following meanings. ·DB Objects···Objects such as tables, stored procedures, triggers, and views stored in a database. ·DB script···A file that describes operation commands for modifying, adding, deleting, etc., 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 resides. · Business system···This is the unit for installing and managing each business application group that is installed in a component-based manner. · Common system: A management unit for functions and applications that are used in common by multiple business systems.
[0018] (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.
[0019] On the other hand, because management is separate, it is difficult to ensure consistency across the entire system, which is a disadvantage. This disadvantage is particularly noticeable when a system is added later or when individual systems are upgraded.
[0020] (3) Overview and Effects of the Invention Therefore, in this embodiment, for example, even though the system is divided into components, an area common to the system and an area for each component are managed separately. With this concept, it is possible to detect inconsistencies and synchronize modules and DB objects used in common by each system at the timing of delivery and system startup.
[0021] This makes it possible to prevent delivery staff responsible for each component from missing patches, ensure the quality of the entire system, and provide speedy, high-quality upgrades. In other words, it has become possible to provide stable service according to the requirements for version updates between business processes when operating business systems, and the usage patterns such as step-by-step introduction and additional introduction for each business system. The specific configuration and operation are explained below.
[0022] [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.
[0023] The synchronization control device 100 is a commercially available desktop personal computer. The synchronization 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, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.
[0024] 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. The units included in the synchronous control device 100 are connected to each other so as to be able to communicate with each other via any communication path.
[0025] The communication interface unit 104 communicatively connects the synchronous control device 100 to a 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 later may be stored in the server 200, for example.
[0026] 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 cooperates with a mouse to realize 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.
[0027] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used as the storage unit 106.
[0028] 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 function and contents of each master will be described in detail in "(3) Master Configuration" in [4. Processing Overview, etc.] below.
[0029] 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 based on these stored programs.
[0030] The control unit 102 conceptually functions as, for example, (1) a DB restoration unit 102a, and (2) a DB object consistency check unit 102b as a DB object consistency check means for checking 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 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 the patch version 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 should be applied. 2b, (3) a DB object synchronization unit 102c as a 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) a patch application unit 102d, (5) a module consistency check unit 102e as 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, and (6) a module synchronization unit 102f as 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.
[0031] The DB restoration unit 102a restores the DB.
[0032] The DB object consistency checking 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.
[0033] Specifically, the DB object consistency check unit 102b performs the following processes (1) to (3).
[0034] (1) The DB object consistency checking unit 102b first obtains the patch version for the source business system for which a flag indicating the need for synchronization (a “true” flag) is set from the applied patch version master 106a, which includes the patch version for the source business system and a synchronization flag.
[0035] (2) The DB object consistency check unit 102b then obtains, from the common system script synchronization management master 106c that includes the source business system and the destination business system, the destination business system that is linked to the source business system that constitutes the patch version obtained in (1).
[0036] (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.
[0037] The DB object synchronization unit 102c applies the applied patch version of the source business system to the destination business system specified by the DB object consistency check unit 102b.
[0038] The patch application unit 102d applies a patch.
[0039] The module consistency check unit 102e checks 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 folder to check whether there is a difference in file version or update date and time.
[0040] Specifically, the module consistency checking unit 102e checks whether there is a difference if there is no file in the folder, or if, by comparing the module master with the folder, the modules have the same module name but the file version or the file update date and time is different.
[0041] More specifically, the module compatibility check unit 102e compares the AP module master 106e and the WEB module master 106f with 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 comparison is made preferentially between the common system distribution module master 106b and the folder for modules identified by the same module name.
[0042] If the module compatibility check unit 102e checks that there is a difference, the module synchronization unit 102f downloads the contents of the module master to the folder.
[0043] 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 at this time, 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 106f to the folder for the modules identified by the same module name.
[0044] [3. Issues, Solutions and Effects] This section describes the problems, solutions, and effects of the present invention.
[0045] (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.
[0046] However, since there are multiple databases, it has the disadvantage that it is difficult to manage module version control and the consistency of database objects.
[0047] In order to address the above disadvantages while enjoying the benefit of being able to use the required version at the required time, one possible approach would be to manage the system separately into separate managed parts and commonly managed parts. By taking this approach, when ensuring the consistency of the entire system, there is no need to consider the separately managed parts, and it is sufficient to focus on the commonly managed parts. However, there are the following issues in automatically controlling the commonly managed parts while satisfying the following requirements:
[0048] The above demands included, for example, the following two points. -Even if the versions and timing of version upgrades for each business system are different, consistency between commonly used modules and DB objects is guaranteed. -Ensure consistency between existing business systems and any business systems added later.
[0049] 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 separate and common control areas. B. How to control synchronization. C. When to synchronize. D. How to detect an inconsistent environment.
[0050] 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.
[0051] (2) Solution of the Invention The solution used in the present invention is as shown in the table in Fig. 4. The table in Fig. 4 shows the management method, synchronization control method, synchronization timing, and inconsistent environment detection method for each module and DB object.
[0052] (3) Effects of the present invention In this embodiment, for example, it is possible to prevent delivery personnel who are divided into different components from missing patches and to ensure the quality of the entire system. As a result, for example, it is possible to provide speedy and high-quality version upgrades.
[0053] [4. Overview of processing, etc.] In this section, an overview of the processing according to this embodiment will be described.
[0054] (1) Purpose In this embodiment, the object is to realize the following 1 and 2 when a business system is introduced, upgraded, and started up. 1. Module Synchronization 2. Synchronizing DB objects
[0055] (2) System Configuration The system configuration in this embodiment will be described.
[0056] 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
[0057] An example of a patch configuration in this embodiment is shown in FIG.
[0058] (3) Master Configuration In this section, the master configuration in this embodiment will be described with reference to FIGS.
[0059] The applied patch version master 106a is a master for managing all patch versions 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, which is composed of the time when the patch version was created or provided and the business system to which the patch version 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. In the following explanation of the master, only records for the common system are shown for the sake of simplicity.
[0060] 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.
[0061] 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 the system dependency. As shown in Fig. 8, the common system script synchronization management master 106c includes, for example, an application source business system and an application destination business system.
[0062] The patch application history master 106d is a master that manages the version of the patch 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), a business system, and the like.
[0063] The AP module master 106e is a master that stores modules of a business system used in an 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.
[0064] The WEB module master 106f is a master that stores modules of a business system used in a WEB server. As shown in Fig. 11, the WEB module master 106f includes, for example, module identification data (module name), file version, arrangement path, module binary information, file update date and time, etc. The explanation of the arrangement path is the same as in the previous paragraph.
[0065] 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."
[0066] (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 a business system is introduced for the first time or when a business system is introduced later will be described in (4-1) below, the processing flow when a version is upgraded will be described in (4-2) below, and the processing flow when the system is started will be described in (4-3) below.
[0067] (4-1) When introducing a new business system or a new business system First, the processing timing is determined (step S1 in FIG. 12). In this item, it is determined that the processing timing is the initial business system introduction time or the subsequent business system introduction time.
[0068] Next, the DB restoration unit 102a performs DB restoration (step S2 in FIG. 12).
[0069] Next, the DB object consistency check unit 102b checks the consistency of the DB object (step S3 in FIG. 12).
[0070] 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).
[0071] 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).
[0072] Next, the module consistency check unit 102e checks the consistency of the module (step S6 in FIG. 12).
[0073] If there is an inconsistency (NG in step S6 in FIG. 12), the module synchronization unit 102f performs a module synchronization process (step S7 in FIG. 12).
[0074] On the other hand, if no inconsistency exists (OK in step S6 in FIG. 12), the process ends (END in FIG. 12).
[0075] (4-2) When upgrading First, the processing timing is determined (step S1 in FIG. 12). In this case, it is determined that the processing timing is a version upgrade timing.
[0076] Next, the DB object consistency check unit 102b checks the consistency of the DB object (step S3 in FIG. 12).
[0077] The process thereafter is the same as in (4-1), so the explanation will be omitted.
[0078] (4-3) At system startup First, the processing timing is determined (step S1 in FIG. 12). In this item, it is assumed that the processing timing is determined to be the system startup time.
[0079] Next, the DB object consistency check unit 102b checks the consistency of the DB object (step S8 in FIG. 12).
[0080] 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).
[0081] On the other hand, if no inconsistency exists (OK in step S8 in FIG. 12), the module consistency check unit 102e performs a consistency check on the module (step S6 in FIG. 12).
[0082] The process thereafter is the same as in (4-1), so the explanation will be omitted.
[0083] (5) Overview of processing In this section, an overview of the processing in this embodiment will be described.
[0084] (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.
[0085] (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.
[0086] 1. First, the DB object consistency check unit 102b extracts rows whose synchronization flags are true from the applied patch version master 106a (that is, obtains a list of patches that require synchronization).
[0087] 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.
[0088] 3. Finally, 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 for each row extracted in 2, 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).
[0089] (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.
[0090] (5-4) Patch application process The patch application unit 102d executes the following steps 1 to 7 in order.
[0091] 1. The patch application unit 102d stores the modules under the common system module folder in the common system distribution module master 106b of the integrated patch management DB.
[0092] 2. The patch application unit 102d stores the modules under the business system AP module folder in the AP module master 106e of the business system DB.
[0093] 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.
[0094] 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 destination business system where the source business system is the "common system."
[0095] 5. The patch application unit 102d applies the DB scripts in the business system script folder to the business system DB.
[0096] 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.
[0097] 7. The patch application unit 102d updates the patch application history master 106d in the business system DB.
[0098] (5-5) Module consistency check process 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.
[0099] 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. Modules that exist in common between the common system distribution module master 106b, the AP module master 106e, and the WEB module master 106f
[0100] When the module to be checked is 1, the module consistency check 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 check 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.
[0101] The module compatibility check unit 102e determines that there is a difference if it corresponds to A or B, and determines that there is no difference otherwise (if it corresponds to neither A nor B).
[0102] In addition, when determining whether or not a module falls under "B," the module compatibility check unit 102e compares the AP module master 106e and the WEB module master 106f with the folder. At this time, 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 between the common system distribution module master 106b and the folder.
[0103] (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.
[0104] [5. Specific examples of processing] This section describes a specific example of the processing according to this embodiment. In this section, the processing at the time of initial business system installation is described in the following [5-1], the processing at the time of version upgrade (when changes are made to DB objects) is described in the following [5-2], the processing at the time of version upgrade (when changes are made to modules) is described in the following [5-3], the processing at the time of subsequent business system installation is described in the following [5-4], and the processing at system startup is described in the following [5-5].
[0105] [5-1. When first introducing a business system] 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.
[0106] (1) Database recovery When each business system is added, the DB restoration unit 102a restores a template DB in the DB server (step S2 in FIG. 12). In this example, as shown in FIG. 13, a situation is considered in which the integrated patch management DB, the personnel system DB, and the payroll system DB are restored.
[0107] (2) DB object consistency check When restoring from a complete system DB 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).
[0108] (3) DB object synchronization processing Since the result of DB object consistency check is OK (there is no inconsistency), DB object synchronization process is not performed.
[0109] (4) Module Integrity Check Immediately after restoring the DB, the module does not exist 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 an inconsistency exists (step S6: NG in FIG. 12).
[0110] (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 consideration the common system distribution module master 106b (if there is a system that you do not want to synchronize, you can deal with it by removing it from the synchronization target folders). 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.
[0111] Since the module consistency check results in OK due to the module synchronization process (OK in step S6 in FIG. 12), the process in this item ends (END in FIG. 12).
[0112] [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].
[0113] (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).
[0114] (2) DB object synchronization processing Since the result of DB object consistency check is OK (there is no inconsistency), DB object synchronization process is not performed.
[0115] (3) Patch application process 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.
[0116] 1. Referring to Figure 16, since there are DB scripts 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 destination business system where the source business system is the "common system".
[0117] 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.
[0118] 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.
[0119] In addition, the following two points will be the same as the environment after completing all steps in [5-1. Initial business system implementation], so we will omit the description here. DB server module master - AP server and WEB server status
[0120] (4) Module Integrity Check It is assumed that the result of the module consistency check is OK (OK in step S6 in FIG. 12).
[0121] (5) Module synchronization processing Since the result of the module consistency check is OK (no inconsistency is found), the module synchronization process is not performed. This completes the process in this item (End in FIG. 12).
[0122] [5-3. When upgrading (when changes are made to the module)] In this section, the process at the time of version upgrade (when a change is made to a module) will be described using Fig. 18 to Fig. 22 while referring to the flowchart in Fig. 12. Note that this section assumes an environment after the completion of all steps in [5-2. At the time of version upgrade (when a change is made to a DB object)].
[0123] (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).
[0124] (2) DB object synchronization processing Since the result of DB object consistency check is OK (there is no inconsistency), DB object synchronization process is not performed.
[0125] (3) Patch application process 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.
[0126] (3-1) Regarding the personnel system 1. The patch application unit 102d stores 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.
[0127] 2. The patch application unit 102d stores the modules under 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 FIG.
[0128] 3. The patch applicator 102d updates the applied patch version master 106a in the integrated patch management DB. Note that, in order to simplify the explanation, the patch application history of the business system is omitted in Fig. 19 .
[0129] 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.
[0130] (3-2) Common Systems 1. The patch application unit 102d stores modules under 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.
[0131] 2. The patch applicator 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.
[0132] Note that the following state will be 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 common system script synchronization management master 106c and era master of DB server
[0133] (4) Module Integrity Check Immediately after applying the patch, an inconsistency occurs between the module master of the DB server and the local folders of the AP server and WEB server (NG in step S6 in FIG. 12). Specifically, FIG. 20 shows the state of the folders in the AP server and WEB server after the patch application process during a version upgrade (when changes are made to the modules), but the contents of FIG. 20 are the same as FIG. 15, which shows the state of the AP server and WEB server after "(5) Module synchronization process" in [5-1. Initial business system installation]. When 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 not yet updated in this section [5-3], the part surrounded by hatching in FIG. 20 corresponds to “B. There is a difference in the file version or the file update date and time” in (5-5) of [4. Overview of processing, etc.], and is the part where the inconsistency occurs (Note that, as shown in FIG. 19, the module consistency check unit 102e compares the common system distribution module master 106b with the folder for the three modules because 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). Therefore, the module consistency check unit 102e determines that an inconsistency exists (NG in step S6 in FIG. 12).
[0134] (5) Module synchronization processing Since the module consistency check is NG (because there is an inconsistency), the module synchronization unit 102f performs the module synchronization process 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 a path designated by the "distribution path." Rule 2: In this case, 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 common system script synchronization management master 106c and era master of DB server
[0135] 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, and at this time, for files set as folders to be synchronized, it performs synchronization control 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 folders to be synchronized). In this example, as shown in Fig. 21, 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 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.
[0136] That is, in principle, 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 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.
[0137] By the above processing, the contents of the Personnel AP Folder \Bin and Payroll AP Folder \Bin on the AP server and the Personnel WEB Folder \Bin and Payroll WEB Folder \Bin on the WEB server are updated as shown in FIG. 22.
[0138] As a result of the module synchronization process, the module consistency check results in OK (OK in step S6 in FIG. 12), and the process ends (END in FIG. 12).
[0139] [5-4. When introducing a new business system] In this section, the process of introducing a new business system will be described with reference to the flowchart in Fig. 12 and Fig. 23 to Fig. 30. Note that this section assumes an environment after the completion of all steps in [5-3. When upgrading (when changes are made to modules)].
[0140] (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).
[0141] (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).
[0142] 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".
[0143] 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.
[0144] 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 "target 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".
[0145] 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
[0146] (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 (step S4 in FIG. 12), as shown in FIG. 25. The DB object synchronization processing results in a DB object consistency check that is OK (OK in step S3 in FIG. 12).
[0147] (4) Module Integrity Check Immediately after the accounting system DB is restored, the accounting system module does not exist on the AP server or 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 an inconsistency exists (step S6: NG in FIG. 12).
[0148] (5) Module synchronization processing Since the module consistency check is NG (because there is an inconsistency), the module synchronization unit 102f performs the module synchronization process 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 a path designated by the "distribution path." Rule 2: In this case, 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 common system script synchronization management master 106c and era master of DB server
[0149] Below, the cases where the synchronization target folder in the synchronization target folder setting file is set and where it is not set will be explained separately.
[0150] (5-1) When a synchronization 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 files 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.
[0151] That is, in principle, 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 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. 26.
[0152] As a result of the above processing, the Personnel 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 Personnel WEB Folder \Bin, Payroll WEB Folder \Bin, and Accounting WEB Folder \Bin on the WEB server are updated as shown in Figure 28.
[0153] As shown in Fig. 27, on the AP server, there is consistency between the Personnel AP Folder\Bin and 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 Personnel WEB Folder\Bin and Payroll WEB Folder\Bin, and the Accounting WEB Folder\Bin.
[0154] As described above in section (5-1), when a synchronization target folder is set in the synchronization target folder setting file, the modules existing in the common system distribution module master 106b are given priority, and the entire system is synchronized as shown in Figures 27 and 28.
[0155] As a result of the module synchronization process, the module consistency check results in OK (OK in step S6 in FIG. 12), and the process ends (END in FIG. 12).
[0156] (5-2) If the synchronization folder is not set If 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.
[0157] As shown in Fig. 29, inconsistencies have occurred between the HR AP folder \Bin and the Payroll AP folder \Bin, and the Accounting AP folder \Bin, on the AP server. Also, as shown in Fig. 30, inconsistencies have occurred between the HR WEB folder \Bin and the Payroll WEB folder \Bin, and the Accounting WEB folder \Bin, on the WEB server.
[0158] 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.
[0159] [5-5. Processing at system startup] In this section, the process at system startup will be described with reference to the flowchart in FIG.
[0160] (1) DB object consistency check Since this involves a system shutdown, automatic synchronization is not assumed, but the DB object consistency check unit 102b may be configured 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 in 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 below.)"
[0161] (2) Module Integrity Check On the other hand, if the result of the DB object consistency check is OK (OK in step S8 in FIG. 12), the module consistency check unit 102e performs a module consistency check. If the module consistency check is forgotten after the patch application process due to a mistake in the delivery process or the like, the result of the module consistency check may be NG (NG in step S6 in FIG. 12).
[0162] (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 during version upgrade (when changes are made to a module)] (step S7 in FIG. 12).
[0163] Since the module consistency check results in OK due to the module synchronization process (OK in step S6 in FIG. 12), the process in this item ends (END in FIG. 12).
[0164] [6. Summary of the present embodiment] In this way, the synchronization control device 100 according to this embodiment can obtain 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.
[0165] [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 contributing to goals 8 and 9 of the SDGs.
[0166] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of goals 12, 13, and 15 of the SDGs.
[0167] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.
[0168] 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.
[0169] 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 known methods.
[0170] In addition, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.
[0171] Moreover, with regard to the synchronous control device 100, the components shown in the figures are merely functional concepts, and the components do not necessarily have to be physically configured as shown in the figures.
[0172] 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 in a non-transient computer-readable recording medium that includes 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 a RAM, and cooperates with the CPU to form a control unit.
[0173] In addition, this computer program may be stored in an application program server connected to the synchronous control device 100 via any network, and it is also possible to download all or part of it as necessary.
[0174] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.
[0175] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, 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 as multiple modules or libraries, and a program that works 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, may use well-known configurations and procedures.
[0176] The various databases etc. stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files etc. used for various processes and providing websites.
[0177] The synchronous control device 100 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as the information processing device to which any peripheral device is connected. The synchronous control device 100 may be realized by installing software (including programs or data) that causes the device to realize the processing described in this embodiment.
[0178] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to 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. [Industrial Applicability]
[0179] The present invention is useful in all industries and business sectors. [Explanation of symbols]
[0180] 100 Synchronous control device 102 Control section 102a DB Recovery Section 102b DB object consistency check section 102c DB object synchronization part 102d Patch Application Department 102e Module Integrity Check Unit 102f Module Synchronization Section 104 Communication interface section 106 Storage section 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 Section 112 Input Devices 114 Output Device 200 Servers 300 Network
Claims
1. 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:
2. 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 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 .
3. 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.
4. 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; The synchronous control device according to claim 3 .
5. 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 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:
6. 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:
7. 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:
Citation Information
Patent Citations
Program patch history management system
JP1988037435A
File processor, file processing system and storage medium
JP2000339211A
Trunk task package and method for selling the same
JP2001195288A
Information processing method, information processor and imaging device
JP2005174130A
Machine tool
JP2016155223A
