JP6519180B2 - Management system, control method, and control program - Google Patents

Description

  The present disclosure relates to control of a management system that manages related information in a consistent manner among a plurality of systems.

  Conventionally, various techniques have been developed for appropriately controlling the execution order of processing. For example, Japanese Patent Application Laid-Open No. 8-272626 (Patent Document 1) discloses a batch job processing method for parallel processing of jobs excluding unnecessary waiting time.

  Japanese Patent Laid-Open Publication No. 9-218861 (Patent Document 2) discloses a scheduler which shortens idle time to wait for another job while holding intermediately generated data of processing when performing scheduling of parallel processing. .

Japanese Patent Application Laid-Open No. 8-272626 Unexamined-Japanese-Patent No. 9-218861

  By the way, in recent years, a management system has been developed which centrally manages usage rights of accounts such as employees and files of employees. The management system automatically generates employee information related to the employee in a plurality of systems (hereinafter, also referred to as “cooperation system”) managed by the self according to the joining, leaving, or transfer of the employee. Update to At this time, if the update process of the employee information is not executed in an appropriate order with respect to each linkage system, the consistency of the employee information may be lost, and as a result, an error may occur.

  In order to avoid such an error, the manager of the management system has to set the order of update processing appropriately for each linkage system. Even if the batch job processing method disclosed in Patent Document 1 or the scheduler disclosed in Patent Document 2 is applied to the management system, the administrator appropriately applies the update processing order to each cooperation system in advance. Should be set to That is, the manager needs knowledge to set the processing order appropriately. Therefore, a management system capable of appropriately updating related information between systems such as employee information with easy settings is desired.

  The present disclosure has been made to solve the problems as described above, and its object is to provide a management system capable of appropriately updating related information between systems with easy settings. It is. An object in another aspect is to provide a control method capable of appropriately updating related information between systems with easy setting. The object in still another aspect is to provide a control program capable of appropriately updating related information between systems with easy setting.

According to one embodiment, the management system respectively holds the first information related to each other, the plurality of systems having a dependency on the update order of the first information of each other, and any one of the plurality of systems. (1) a first receiving unit for receiving an update to the information, a second receiving unit for receiving, as a dependency, settings related to a plurality of systems , and a dependency when the first receiving unit receives an update A determination unit for determining the update order of each of the first information held in the plurality of systems based on the contents of the update, and the update order determined by the determination unit is held in the plurality of systems And an updating unit for updating each of the first information.

  Preferably, the determination unit identifies the dependent system for each of the plurality of systems based on the dependency and the content of the update, and updates the system to preferentially update the first information in the dependent system. Determine the order.

  Preferably, the contents of the update include new creation of the first information and deletion of the first information. The multiple systems have a hierarchical relationship with one another. When the content of the update is the creation of new information of the first information, the determination unit identifies, for each of a plurality of systems, a system having a higher hierarchy than that system as a dependent system, and the content of the update In the case of deletion of the first information, for each of a plurality of systems, a system lower in hierarchy than the system is specified as a dependent system.

  Preferably, when the updating unit fails in the middle of the process of sequentially updating each of the first information held in the plurality of systems in the updating order determined by the determining unit, the updating unit performs the first process on the system. Do not make subsequent updates to the information.

  Preferably, the plurality of systems each hold second information related to each other. The determination unit further determines the update order of each of the second information held in the plurality of systems based on the dependency and the content of the update to the second information. The update unit updates the first information and the second information in parallel, when the update timing of the first information and the update timing of the second information overlap between different systems.

According to another aspect, the management system holds the first information related to each other, the plurality of systems having a dependency on the update order of the first information of each other, and any one of the plurality of systems. A first accepting unit for accepting an update to information, and each of first information held in a plurality of systems based on the dependency and the contents of the update when the first accepting unit accepts an update A determination unit for determining the update order, and an update unit for updating each of the first information held in the plurality of systems in the update order determined by the determination unit. The contents of the update include the change of the first information. The change is realized by the deletion process of the first information and the new creation process of the new first information. The management system receives a setting as to which of the deletion process and the new creation process is to be prioritized.
According to another aspect, the management system holds the first information related to each other, the plurality of systems having a dependency on the update order of the first information of each other, and any one of the plurality of systems. A first accepting unit for accepting an update to information, and each of first information held in a plurality of systems based on the dependency and the contents of the update when the first accepting unit accepts an update A determination unit for determining the update order, and an update unit for updating each of the first information held in the plurality of systems in the update order determined by the determination unit. The plurality of systems each hold second information related to each other. The determination unit further determines the update order of each of the second information held in the plurality of systems based on the dependency and the content of the update to the second information. When the update timing of the first information and the update timing of the second information overlap between different systems , the update unit updates the first information and the second information in parallel, and the update timing of the first information and the first information When the update timings of the two pieces of information overlap in the same system, the information having the larger number of systems depending on the first information and the second information is preferentially updated.

According to another aspect, a control method of a management system is provided. The management system comprises a plurality of systems each holding first information related to each other and having a dependency on the update order of the first information of each other. The control method includes a step of receiving an update to first information of any of a plurality of systems, a step of receiving a setting of an association between the plurality of systems as a dependency, and a dependency and an update when the update is accepted. Determining an update order of each of the first information held in the plurality of systems based on the contents of: and updating each of the first information held in the plurality of systems in the update order; Equipped with

According to still another aspect, a control program of a management system is provided. The management system comprises a processor and a plurality of systems each holding first information related to each other and having a dependency on the update order of the first information of each other. The control program depends on the processor in receiving the update to the first information of any one of the plurality of systems , receiving the setting of the relation between the plurality of systems as a dependency, and receiving the update. Determining the update order of the first information held in the plurality of systems based on the relationship and the contents of the update, and updating each of the first information held in the plurality of systems in the update order And execute the following steps.

  In one aspect, related information between systems can be appropriately updated with easy settings.

  The above and other objects, features, aspects and advantages of the present invention will become apparent from the following detailed description of the present invention taken in conjunction with the accompanying drawings.

It is a figure showing an example of system configuration of a management system. It is a conceptual diagram showing roughly processing of an ID (Identification) integrated system according to a 1st embodiment. It is a block diagram showing functional composition of an ID unification system according to a 1st embodiment. It is a figure which shows an example of the dependency between systems. It is a figure which shows the content of the update information output by the update reception part. It is a figure which shows the content of the update list | wrist output by the specific part. It is a figure which shows the content of the process order list | wrist output by the determination part. It is a figure which shows the content of the process order list | wrist in the process of performing an update process. It is a figure which shows the content of the process order list | wrist in the process of performing an update process. It is the figure which compared the time from the start of an update process until completion in the ID integrated system according to 1st Embodiment, and the conventional ID integrated system. It is a flowchart showing the process which the ID integrated system according to the first embodiment executes. It is a block diagram which shows the main hardware constitutions of a management system. It is a figure which shows the content of the processing order list in 2nd Embodiment. It is the figure which showed the update process performed in each system in order of time series.

  Hereinafter, embodiments according to the present invention will be described with reference to the drawings. In the following description, the same parts and components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed description of these will not be repeated. In addition, the embodiments or modifications described below may be selectively combined as appropriate.

First Embodiment
System Configuration of Management System 500
The system configuration of the management system 500 will be described with reference to FIG. FIG. 1 is a diagram showing an example of a system configuration of a management system 500. As shown in FIG.

  As illustrated in FIG. 1, the management system 500 includes an ID integrated system 100, linkage systems 300A to 300C, and a DB (DataBase) server 400. The ID integrated system 100 and the DB server 400 are connected to each other via the network 140A. The ID integrated system 100 and the cooperation systems 300A to 300C are connected to each other via the network 140B.

  The management system 500 is used, for example, to centrally manage employee information in a company. As an example, the employee information includes, for each employee ID, the correspondence between the employee ID, the name of the employee, the email address of the employee, and the access authority of the folder of the employee. The administrator performs an operation on the ID integrated system 100 to update the employee information managed by the DB server 400 according to the joining, leaving, or transfer of the employee. When the ID integrated system 100 receives the operation, the ID integrated system 100 automatically updates the employee information on the employee in the collaboration systems 300A to 300C. Thereby, ID integrated system 100 maintains consistency of employee information among cooperation systems 300A-300C. The ID integrated system 100 periodically and collectively performs update processing at a predetermined time such as night, for example. The update process includes, for example, an employee information registration process, a deletion process, and a change process.

  Although the following description will be made with employee information as information managed by the management system 500, the information is not limited to the employee information. For example, the information may be user information or other information.

[Overview of ID integrated system 100]
An overview of the ID integrated system 100 will be described with reference to FIG. FIG. 2 is a conceptual view schematically showing the process of the ID integrated system 100. As shown in FIG. In order to simplify the description, in FIG. 2, an example in which the management system 500 is configured by two cooperation systems 300A and 300B will be described.

  The cooperation system 300A holds employee information 222A. The collaboration system 300B holds employee information 222B. The employee information 222A, 222B is information related to each other, and has a dependency in the update order of each other. That is, the employee information 222A and 222B mutually share information that is common at least in part. Therefore, when the ID integrated system 100 does not update the employee information 222A, 222B in an appropriate order, the integrity of the employee information 222A, 222B is lost, resulting in an error.

  A specific example where such an error occurs will be described. For example, it is assumed that the linkage system 300A is an AD (Active Directory) server and the linkage system 300B is a file server. In addition, it is assumed that the administrator newly creates a new employee account (employee ID etc.) and the authority of the employee to the AD server, and another administrator adds the folder authority to the employee to the file server. . In this case, since the file server needs to acquire the authority of the employee from the AD server, the process of newly creating the account of the employee needs to be performed prior to the process of adding the authority of the employee. . As described above, since the file server employee information depends on the AD server employee information, in order to update the employee information 222A, 222B while maintaining the integrity, the ID integrated system 100 needs the employee information 222A, It is necessary to execute update processing after grasping the mutual dependency of 222B.

  Therefore, when the ID integrated system 100 according to the present embodiment receives an update to any one of the employee information 222A and 222B, the ID integrated system 100 is based on the dependency between the employee information 222A and 222B and the updated content of the employee information 222A and 222B. The order of updating the employee information 222A and 222B is determined.

  More specifically, the ID integrated system 100 identifies the dependent system of each system based on the inter-system dependency and the updated content, and preferentially updates the employee information in the dependent system. The dependent system is identified according to the following rules (1) to (3).

  Rule (1): When the update content is newly created, for each system, a system in a higher hierarchy than the system is specified as a dependent system.

  Rule (2): When the update content is deletion, for each system, a system in a lower hierarchy than the system is specified as a dependent system.

  Rule (3): When the update content is a change, for each system, a system in a higher hierarchy than the system is specified as a dependent system.

  For example, it is assumed that the collaboration system 300A and the collaboration system 300B have a hierarchical relationship, and the collaboration system 300A is a higher system and the collaboration system 300B is a lower system. In this case, when executing the new creation process and the change process of the employee information, the ID integrated system 100 specifies the cooperation system 300A as the dependency destination of the cooperation system 300B according to the above-mentioned rules (1) and (3) (FIG. 2) Processing example of (see (A)). As a result, the ID integrated system 100 updates the employee information 222A of the collaboration system 300A, which is the dependency destination of the collaboration system 300B, and then updates the employee information 222B of the collaboration system 300B.

  On the other hand, when executing the deletion process of the employee information, the ID integrated system 100 specifies the cooperation system 300B as the dependency destination of the cooperation system 300A according to the above-mentioned rule (2) (see process example (B) in FIG. 2). . As a result, the ID integrated system 100 updates the employee information 222B of the collaboration system 300B, which is the dependency destination of the collaboration system 300A, and then updates the employee information 222A of the collaboration system 300A.

  As described above, the ID integrated system 100 identifies the dependency destination system of each collaboration system based on the dependency between the collaboration systems and the update content, and preferentially updates the employee information in the dependency destination system.

  The ID integrated system 100 can appropriately update each employee information only by setting the dependency (hierarchical relationship) between the linkage systems. Since the dependency between the collaboration systems can be easily understood by the manager, even a manager without knowledge can easily set the dependency between the collaboration systems. This eliminates the need for the administrator to set the update order for each linkage system, and as a result, it is possible to prevent the setting error of the update order. The dependency between the collaboration systems may be determined in advance by a designer when designing the management system 500.

[Functional configuration of ID integrated system 100]
The functions of the ID integrated system 100 according to the first embodiment will be described with reference to FIGS. 3 to 10. FIG. 3 is a block diagram showing a functional configuration of the ID integrated system 100. As shown in FIG. As shown in FIG. 3, the ID integrated system 100 includes a program 130. The program 130 is stored, for example, in the storage device 110 (FIG. 12) of the ID integrated system 100. The program 130 is executed by, for example, a CPU (Central Processing Unit) 102 of the ID integrated system 100. The program 130 includes a dependency relationship receiving unit 150 (second receiving unit), an update receiving unit 160 (first receiving unit), a specifying unit 170, a determining unit 180, and an updating unit 190. Below, these functions are explained in order.

(Dependency reception unit 150)
The function of the dependency relationship receiving unit 150 will be described with reference to FIGS. 3 and 4. FIG. 4 is a diagram showing an example of dependency between systems. In the example of FIG. 4, the management system 500 is configured by cooperation systems 300A to 300E.

  As shown in FIG. 3, the dependency receiving unit 150 receives an input of dependency between systems by the administrator. That is, the administrator can set the dependency between the collaboration systems 300A to 300E on the management system 500. In other words, the administrator sets the hierarchy of each collaboration system. Upon receiving the dependency between the collaboration systems, the dependency receiving unit 150 outputs the dependency to the determining unit 180.

  As the setting method of the dependency, for example, as shown in FIG. 4, there is a method of connecting the respective cooperation systems by connecting the respective cooperation systems with a line or the like. In the example of FIG. 4, the collaboration system 300A and the collaboration system 300B are associated with each other. The cooperation system 300A and the cooperation system 300D are associated with each other. The cooperation system 300B and the cooperation system 300C are associated with each other. The cooperation system 300D and the cooperation system 300E are associated with each other.

(Update acceptance unit 160)
The function of the update receiving unit 160 will be described with reference to FIGS. 3 and 5. FIG. 5 is a diagram showing the contents of the update information 51 output by the update receiving unit 160. As shown in FIG.

  The above-mentioned DB server 400 (see FIG. 1) extracts, as update information 51, employee information whose database has been updated. That is, in the update information 51, the contents of change in employee information are summarized. For example, when the DB server is a personnel system, the personnel system usually has a function of generating update information 51 as a basic function. In the example of FIG. 5, the update information 51 includes update information indicating “joining” of an employee whose employee ID is “1”, update information indicating “department change” of an employee whose employee ID is “2”, It has the update information which shows "retirement" of the employee whose employee ID is "3". The DB server 400 periodically transmits the update information 51 to the ID integrated system 100 at a predetermined time such as night.

  As shown in FIG. 3, the update receiving unit 160 receives, from the DB server 400, the update information 51 in which the update content is organized. The update accepting unit 160 outputs the received update information 51 to the identifying unit 170.

(Specification section 170)
The function of the identifying unit 170 will be described with reference to FIGS. 3, 5 and 6. FIG. 6 is a diagram showing the contents of the update list 53 output by the identifying unit 170. As shown in FIG.

  The identifying unit 170 identifies a linkage system to be a target for updating employee information based on the above-described update information 51 (see FIG. 5), and identifies the update content. More specifically, the identification unit 170 first identifies a collaboration system using the employee ID included in the update information 51.

  In the example of FIG. 6, the identifying unit 170 identifies the collaboration systems 300A to 300C that use the employee ID “1” included in the update information 51 of FIG. 5 as a system to be updated. Further, since the update information 51 indicates that the change content of the employee ID “1” is “join”, the identifying unit 170 is an employee of the employee ID “1” with respect to the collaboration systems 300A to 300C. Judge to create new information.

  Similarly, the identifying unit 170 identifies the collaboration systems 300B and 300C using the employee ID “2” included in the update information 51 as the system to be updated. Further, since the update information 51 indicates that the change content of the employee ID "2" is "department change", the identifying unit 170 transmits the employee information to the cooperation system 300A, 300B. Identify that the employee information in "2" is "changed".

  Similarly, the specifying unit 170 specifies the collaboration systems 300A to 300E using the employee ID “3” included in the update information 51 as the system to be updated. Further, since the update information 51 indicates that the change content of the employee ID “3” is “retirement”, the identifying unit 170 is an employee of the employee ID “3” with respect to the collaboration systems 300A to 300E. Judge to delete information.

  As described above, the identification unit 170 identifies the system to be updated and the update content for each system, and generates the update list 53. As shown in FIG. 3, the identifying unit 170 outputs the generated update list 53 to the determining unit 180.

(Determination unit 180)
The function of the determination unit 180 will be described with reference to FIGS. 4 and 7. FIG. 7 is a diagram showing the contents of the process order list 55 output by the determination unit 180. As shown in FIG.

  The determination unit 180 determines the dependent system of each collaboration system based on the dependency between the collaboration systems and the update content. At this time, the determination unit 180 determines the dependent system of each cooperation system according to the above-described rules (1) to (3).

  For example, when the update content is “newly created”, the determination unit 180 further performs cooperation in a higher hierarchy in the collaboration systems 300A to 300C which are targets to be subjected to the new creation process according to the above-described rule (1). Determine a system as a dependent system. The hierarchical relationship between systems is as shown in FIG. As a result, as shown in the processing order list 55 of FIG. 7, the determining unit 180 determines that the dependent of the cooperation system 300C is the cooperation system 300B of the upper layer. Similarly, the determination unit 180 determines that the dependency destination of the collaboration system 300B is the collaboration system 300A of the upper layer.

  In addition, when the update content is “change”, the determination unit 180 performs a process in a higher hierarchy in each of the cooperation systems 300B and 300C which are targets of the change process according to the above-described rule (3). To be the dependent system. As a result, as shown in the processing order list 55 of FIG. 7, the determining unit 180 determines that the dependent of the cooperation system 300C is the cooperation system 300B of the upper layer.

  Furthermore, when the update content is “deletion”, the determination unit 180 is in a lower hierarchy with respect to each of the cooperation systems 300A to 300E which are targets to be subjected to the deletion process according to the above-described rule (2). Determine a system as a dependent system. As a result, as shown in the processing order list 55 of FIG. 7, the determining unit 180 determines that the dependent of the cooperation system 300A is the cooperation systems 300B and 300C of the lower layer. Similarly, the determination unit 180 determines that the dependency destination of the collaboration system 300B is the collaboration system 300C of the lower layer. Similarly, the determination unit 180 determines that the dependency destination of the collaboration system 300E is the collaboration system 300D of the lower layer.

(Update unit 190)
The function of the updating unit 190 will be described with reference to FIGS. 8 and 9 show the contents of the processing order list 55 in the process of executing the update processing. FIG. 10 is a diagram comparing the time from start to completion of the update process (hereinafter also referred to as “update time”) in the ID integrated system 100 according to the present embodiment and the conventional ID integrated system. is there. More specifically, the comparison result (A) of FIG. 10 is a diagram showing the update time of the ID integrated system 100 according to the present embodiment. The comparison result (B) of FIG. 10 is a figure showing the update time of the conventional ID integrated system.

  The updating unit 190 executes the updating process of each of the cooperation systems 300A to 300E with reference to the processing order list 55 output by the above-described determining unit 180. At this time, the updating unit 190 preferentially executes tasks having fewer dependent tasks.

  In the example of FIG. 8, the updating unit 190 first performs a new creation process (task No. 1) for the collaboration system 300A, a change process (task No. 4) for the collaboration system 300B, a deletion process (task No. 8) for the collaboration system 300C, and the collaboration system Execute deletion process (task No. 9) for 300D preferentially. At this time, since these update processes can be executed by different systems, the update unit 190 executes these update processes in parallel.

  In other words, when the update timing of one employee information (first employee information) and the update timing of another employee information (second employee information) overlap between different systems, the updating unit 190 (1) Updating the employee information and the second employee information in parallel, whereby the processing time can be shortened.

  The update unit 190 sequentially sets the “state” of each task to “completion” at the timing when the update process in each of the tasks No. 1, No. 4, No. 8 and No. 9 is completed. At the same time, the updating unit 190 deletes the terminated task from the dependent task. For example, when task No. 1 is completed, the updating unit 190 deletes the completed task No. 1 from the task to which the task No. 2 depends. Similarly, the updating unit 190 deletes the completed task No. 4 from the task to which the task No. 5 depends. Similarly, the updating unit 190 deletes the completed task No. 9 from the tasks to which the task No. 6 and the task No. 10 depend. Similarly, the updating unit 190 deletes the completed task No. 8 from the task to which the task No. 7 depends. Thus, the processing order list 55 is updated as shown in FIG.

  As a result, the updating unit 190 newly performs a new creation process (task No. 2) for the collaboration system 300B, a change process (task No. 5) for the collaboration system 300C, a deletion process (task No. 7) for the collaboration system 300B, and a process for the collaboration system 300E. It becomes possible to execute deletion processing (task No. 10). At this time, task No. 2 and task No. 7 can not be executed at the same time since they are executed by the same cooperation system 300B. Therefore, the updating unit 190 executes one of task No. 2 and task No. 7 and task Nos. 5 and 10 in parallel.

  As described above, the updating unit 190 causes each of the collaboration systems 300A to 300E to execute the employee information updating process in parallel. As a result, as shown in the comparison result (A) of FIG. 10, the ID integrated system 100 can end the update process at time T1. On the other hand, since the conventional ID integrated system sequentially executes the update process, the update process is ended at time T2 after time T1. As described above, the ID integrated system 100 according to the present embodiment can complete the update processing in a short time as compared with the conventional ID integrated system by processing each task in parallel.

[Control structure of ID integrated system 100]
The control structure of the ID integrated system 100 according to the first embodiment will be described with reference to FIG. FIG. 11 is a flowchart showing the process executed by the ID integrated system 100. The process of FIG. 11 is realized by the CPU 102 (see FIG. 12) of the ID integrated system 100 executing the program 130 (see FIG. 3). In another aspect, part or all of the processing may be performed by circuit elements or other hardware.

  In step S10, the CPU 102 receives the setting of inter-system dependency as the above-described dependency receiver 150 (see FIG. 3).

  In step S20, the CPU 102 determines whether the update information 51 (see FIG. 5) has been received from the DB server 400 as the above-described update receiving unit 160 (see FIG. 3). When the CPU 102 determines that the update information 51 has been received from the DB server 400 (YES in step S20), the control is switched to step S22. If not (NO in step S20), CPU 102 executes the process of step S20 again.

  In step S22, the CPU 102 specifies the update target system from among the cooperation systems 300A to 300E based on the update information 51 as the above-described identification unit 170 (see FIG. 3).

  In step S24, the CPU 102 determines the update order for each of the employee information held in the collaboration systems 300A to 300E based on the inter-system dependency and the update content as the determination unit 180 (see FIG. 3) described above. decide. Since the method of determining the update order is as described above, the description will not be repeated.

  In step S26, the CPU 102 updates each of the employee information held in the collaboration systems 300A to 300E in the determined update order as the above-described update unit 190 (see FIG. 3).

  At this time, when the update timing of a certain employee information (first employee information) and the update timing of another employee information (second employee information) overlap in a system different from each other in the system, the first employee information and the second employee information Update employee information in parallel. Further, when the update order of the first employee information and the update order of the second employee information overlap in the same system, the CPU 102 depends on each of the first employee information and the second employee information. Update the information with the larger number preferentially.

  When the updating process fails in the process of sequentially updating each of the employee information in the determined updating order, the CPU 102 does not perform subsequent updating of the employee information on the system. That is, the CPU 102 interrupts the updating process when the updating process fails halfway.

[Hardware configuration of management system 500]
An example of the hardware configuration of the management system 500 will be described with reference to FIG. FIG. 12 is a block diagram showing the main hardware configuration of the management system 500. As shown in FIG. As shown in FIG. 12, the management system 500 includes an ID integrated system 100, a linkage system 300, and a DB server 400. The cooperation system 300 corresponds to the above-described cooperation systems 300A to 300E. The ID integrated system 100, the linkage system 300, and the DB server 400 are connected to one another via a network 140. The hardware configuration of the ID integrated system 100, the hardware configuration of the cooperation system 300, and the hardware configuration of the DB server 400 will be described in order below.

(Hardware configuration of the ID integrated system 100)
As shown in FIG. 12, the ID integrated system 100 includes a ROM (Read Only Memory) 101, a CPU 102, a RAM (Random Access Memory) 103, a network interface (I / F) 104, a monitor 105, and storage. And an apparatus 110.

  The ROM 101 stores an operating system, a control program executed by the ID integrated system 100, and the like. The CPU 102 controls the operation of the ID integrated system 100 by executing various programs such as an operating system (OS: Operating System) and a control program of the ID integrated system 100. The RAM 103 functions as a working memory, and temporarily stores various data necessary for program execution.

  An antenna (not shown) or the like is connected to the network I / F 104. The ID integrated system 100 transmits and receives data to and from another communication device via the antenna. Other communication devices include, for example, the cooperation system 300, the DB server 400, and other communication devices. The ID integrated system 100 may be configured to be able to download a program for realizing various processes according to the present embodiment.

  The monitor 105 displays the employee information stored in the ID integrated system 100 in such a manner that the manager can confirm it. The monitor 105 may be realized as a touch panel in combination with a touch sensor (not shown). The touch panel receives an update of employee information managed by the ID integrated system 100 by a touch operation.

  The storage device 110 is, for example, a storage medium such as a hard disk or an external storage device. As an example, storage device 110 has a program 130 for realizing various processes according to the present embodiment, employee information 222A (see FIG. 2) managed by ID integrated system 100, and a dependency between systems. And store the indicated information. The program 130, the employee information 222A, and the dependency may be stored not in the storage device 110 but in the DB server 400 or another server.

  Note that the program 130 for realizing various processes according to the present embodiment may be provided as part of an arbitrary program rather than as a single program. In this case, the process according to the present embodiment is realized in cooperation with an arbitrary program. Even a program that does not include such a part of modules does not deviate from the spirit of the ID integrated system 100 according to the present embodiment. Furthermore, some or all of the functions provided by the program 130 according to the present embodiment may be realized by dedicated hardware. Furthermore, the ID integrated system 100 and the server may cooperate to realize the process according to the present embodiment. Furthermore, the ID integrated system 100 may be configured as a so-called cloud service in which at least one server implements the process according to the present embodiment.

(Linkage system 300 hardware configuration)
Next, the hardware configuration of the cooperation system 300 will be described. As shown in FIG. 12, the cooperation system 300 includes a ROM 201, a CPU 202, a RAM 203, a network I / F 204, and a storage device 210.

  The ROM 201 stores an operating system, a control program executed by the linkage system 300, and the like. The CPU 202 controls the operation of the cooperation system 300 by executing various programs such as an operating system and a control program of the cooperation system 300. The RAM 203 functions as a working memory, and temporarily stores various data necessary for program execution.

  An antenna (not shown) or the like is connected to the network I / F 204. The cooperation system 300 transmits / receives data to / from another communication device via the antenna. Other communication devices include, for example, the ID integrated system 100, the DB server 400, and other communication devices.

  The monitor 205 displays the employee information stored in the linkage system 300 in such a manner that the manager can confirm it. The monitor 205 may be realized as a touch panel in combination with a touch sensor (not shown). The touch panel receives an update of employee information managed by the cooperation system 300 by a touch operation.

  The storage device 210 is, for example, a storage medium such as a hard disk or an external storage device. As an example, the storage device 210 stores a program executed by the cooperation system 300, employee information 222A (see FIG. 2) and the like managed by the cooperation system 300.

(Hardware configuration of DB server 400)
Next, the hardware configuration of the DB server 400 will be described. As illustrated in FIG. 12, the DB server 400 includes a ROM 401, a CPU 402, a RAM 403, a network I / F 404, and a storage device 410.

  The ROM 401 stores an operating system, a control program executed by the DB server 400, and the like. The CPU 402 controls the operation of the DB server 400 by executing various programs such as an operating system and a control program of the DB server 400. The RAM 403 functions as a working memory, and temporarily stores various data required for program execution.

  An antenna (not shown) or the like is connected to the network I / F 404. The DB server 400 transmits and receives data to and from other communication devices via the antenna. Other communication devices include, for example, the ID integrated system 100, the linkage system 300, and other communication devices.

  The monitor 405 displays the employee information stored in the DB server 400 in such a manner that the administrator can confirm it. The monitor 405 may be realized as a touch panel in combination with a touch sensor (not shown). The touch panel receives an update of employee information managed by the DB server 400 by a touch operation.

  The storage device 410 is, for example, a storage medium such as a hard disk or an external storage device. As an example, the storage device 410 stores a program executed by the DB server 400, employee information managed by the DB server 400, and the like.

Second Embodiment
[Overview]
The ID integrated system 100 according to the first embodiment dynamically updates the employee information of each system based on the state of each task. On the other hand, the ID integrated system 100 according to the second embodiment collectively determines the update order of each cooperation system based on the dependency between the cooperation systems. The other points such as the hardware configuration of ID integrated system 100 according to the second embodiment are the same as ID integrated system 100 according to the first embodiment, and therefore, the description thereof will not be repeated.

  Hereinafter, a method of determining the update order in the second embodiment will be described with reference to FIGS. 13 and 14. FIG. 13 is a diagram showing the contents of the processing order list 55A in the second embodiment. FIG. 14 is a diagram showing update processing executed in the collaboration systems 300A to 300E in chronological order.

  The ID integrated system 100 according to the present embodiment determines the update order of each cooperation system based on the following rules (4) to (6).

  Rule (4): The ID integrated system 100 preferentially executes tasks with fewer dependent tasks.

  Rule (5): In the case where the update order is not uniquely determined by rule (4), the ID integrated system 100 has a larger number of dependent tasks (hereinafter, also referred to as “dependent task number”). Execute tasks with priority.

  Rule (6): In the case where the update order is not uniquely determined by the rule (5), the ID integrated system 100 preferentially executes tasks with a deeper depth of dependent tasks. The term "depth" as used herein refers to the number of dependent tasks.

  In the example of FIG. 13, the ID integrated system 100 executes task No. 1, No. 4, No. 8, No. 9 with priority depending on the task (1) with fewer dependent tasks, ie, no dependent tasks, according to the above rule (4). Do.

  Next, the ID integrated system 100 applies the rule (5) to the tasks No. 1, No. 4, No. 8 and No. 9 whose update order has not been determined uniquely. In task No. 1, the dependent task numbers are two, task No. 2 and task No. 3. The number of dependent tasks of task No. 4 is one of task No. 5. The number of dependent tasks of task No. 8 is two, that is, task Nos. 6 and 7. The number of dependent tasks of task No. 9 is two, that is, task Nos. 6 and 10. The ID integrated system 100 executes task numbers No. 1, No. 8 and No. 9 with a larger number of dependent tasks prior to task No. 4 in priority. As a result, the ID integrated system 100 executes task No. 4 fourth.

  Next, the ID integrated system 100 applies the rule (6) to the tasks No1, No8 and No9. Task No. 1 is indirectly dependent on task No. 3 via task No. 2. Therefore, the depth of the dependent task of task No. 1 is "2". Task No. 8 is indirectly dependent on task No. 6 via task No. 7. Therefore, the depth of the dependent task of task No. 8 is "2". The task No. 9 is directly dependent on the task Nos. 6 and 10. Therefore, the dependent depth of task No. 9 is “1”. The ID integrated system 100 executes task Nos. 1 and 8 with a deeper dependent task depth prior to task No. 9 in priority. As a result, the ID integrated system 100 executes task No. 9 third.

  Note that any task may be executed first for task Nos. 1 and 8 for which the execution order has not been determined by the rules (4) to (6). In the example of FIG. 13, the ID integrated system 100 preferentially executes task No. 1 over task No. 8. That is, the ID integrated system 100 executes task No. 1 first, and executes task No. 8 second.

  The ID integrated system 100 applies the rules (4) to (6) to all tasks specified in the processing order list 55A, and determines the execution order of each task. Thus, the ID integrated system 100 executes task Nos. 1 to 10 in the order shown in FIG.

Third Embodiment
As described above, the update process includes the employee information registration process, the deletion process, and the change process. Here, in the first embodiment, the change process of the employee information is premised on the change by the overwrite process. However, depending on the cooperation system, there are cases where the change process can not be realized by the overwrite process. In this case, after deleting the existing employee information, the ID integrated system 100 realizes the change processing by newly creating the post-change employee information in the linkage system. That is, the change processing is realized by deletion processing of employee information and new creation processing of new employee information. The ID integrated system 100 according to the third embodiment receives a setting as to which of the deletion process and the new creation process is to be prioritized.

  For example, when changing data with uniqueness restrictions (unique data), the ID integrated system 100 can not change the content of the data until after deleting the data. Therefore, the ID integrated system 100 executes the deletion process of the data, and then executes a new creation process of the data after the change. In such a case, the ID integrated system 100 makes the new creation process dependent on the deletion process in order to prioritize the deletion process over the new creation process.

  On the other hand, when changing data having no uniqueness restriction, the ID integrated system 100 gives priority to the new creation process of the data over the deletion process of the data. This is because, when the deletion process is executed before the new creation process, the deleted data can not be restored if a problem occurs during the process. In such a case, the ID integrated system 100 relies on the new creation process for the deletion process in order to prioritize the new creation process over the deletion process.

Fourth Embodiment
The ID integrated system 100 according to the fourth embodiment preferentially executes tasks with more dependent tasks if there are multiple tasks that can be processed in the same system. In other words, in the ID integrated system 100, when the update timing of certain employee information (first employee information) and the update timing of other employee information (second employee information) overlap in the same system, the first employee The information with the larger number of linkage systems depending on each of the information and the second employee information is preferentially updated. As a result, the ID integrated system 100 can preferentially execute tasks having a large number of dependent tasks, and can accelerate the execution of subsequent tasks. As a result, the ID integrated system 100 can reduce the overall processing time.

  It should be understood that the embodiments disclosed herein are illustrative and non-restrictive in every respect. The scope of the present invention is indicated not by the above description but by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

  51 update information, 53 update list, 55, 55A processing order list, 100 integrated system, 101, 201, 401 ROM, 102, 202, 402 CPU, 103, 203, 403 RAM, 104, 204, 404 network I / F, 105, 205, 405 monitor, 110, 210, 410 storage device, 122A, 222A employee information, 140, 140A, 140B network, 150 dependency relationship reception unit, 160 update reception unit, 170 identification unit, 180 determination unit, 190 update unit , 300A-300E linkage system, 400 DB server, 500 management system, No1 to No10 task, T1, T2 time.

Claims (9)

A management system,
A plurality of systems each holding first information related to each other and having a dependency on the update order of the first information of each other;
A first accepting unit for accepting an update to first information of any one of the plurality of systems;
A second accepting unit for accepting, as the dependency, the setting of the relationship between the plurality of systems;
When the first reception unit receives the update, a determination is made to determine the update order of the first information held in the plurality of systems based on the dependency and the content of the update Department,
A management system, comprising: an update unit for updating each of the first information held in the plurality of systems in the update order determined by the determination unit. The determination unit is
The dependent system is identified for each of the plurality of systems based on the dependency and the contents of the update,
The management system according to claim 1, wherein the update order is determined to update first information in the dependent system preferentially. The contents of the update include new creation of the first information and deletion of the first information,
The plurality of systems have a hierarchical relationship with each other,
The determination unit is
When the content of the update is a new creation of the first information, for each of the plurality of systems, a system having a hierarchy higher than that of the system is specified as the dependent system,
The system according to claim 2 , wherein when the content of the update is deletion of the first information, a system lower in hierarchy than the system is specified as the system to which the dependency is directed for each of the plurality of systems. Management system. When the updating process fails during the process of updating each of the first information held in the plurality of systems in order in the updating order determined by the determining unit, the updating unit performs the first process on the system. The management system according to any one of claims 1 to 3 , wherein the information is not updated thereafter. The plurality of systems each hold second information related to each other,
The determination unit further determines the update order of each of the second information held in the plurality of systems based on the dependency and the content of the update on the second information,
The update unit updates the first information and the second information in parallel, when the update timing of the first information and the update timing of the second information overlap between different systems. The management system according to any one of ~ 4 . A management system,
A plurality of systems each holding first information related to each other and having a dependency on the update order of the first information of each other;
A first accepting unit for accepting an update to first information of any one of the plurality of systems;
When the first reception unit receives the update, a determination is made to determine the update order of the first information held in the plurality of systems based on the dependency and the content of the update Department,
An updating unit for updating each of the first information held in the plurality of systems in the update order determined by the determining unit;
The content of the update includes a change of the first information,
The change is realized by deletion processing of the first information and new creation processing of new first information,
The management system, which receives a setting as to which of the deletion process and the new creation process is to be prioritized. A management system,
A plurality of systems each holding first information related to each other and having a dependency on the update order of the first information of each other;
A first accepting unit for accepting an update to first information of any one of the plurality of systems;
When the first reception unit receives the update, a determination is made to determine the update order of the first information held in the plurality of systems based on the dependency and the content of the update Department,
An updating unit for updating each of the first information held in the plurality of systems in the update order determined by the determining unit;
The plurality of systems each hold second information related to each other,
The determination unit further determines the update order of each of the second information held in the plurality of systems based on the dependency and the content of the update on the second information,
The updating unit is
When the update timing of the first information and the update timing of the second information overlap between different systems, the first information and the second information are updated in parallel,
When the update timing of the first information and the update timing of the second information overlap in the same system, the number of systems depending on each of the first information and the second information is larger Management system to update information preferentially. A control method of a management system,
The management system comprises a plurality of systems each holding first information related to each other and having a dependency on the update order of the first information of each other.
The control method is
Accepting an update to first information of any of the plurality of systems;
Accepting as the dependency relationship settings between the plurality of systems;
Determining an update order of each piece of first information held in the plurality of systems based on the dependency and the contents of the update when the update is received;
Updating each of the first information held in the plurality of systems in the update order. Control program of management system,
The management system
A processor,
A plurality of systems each holding first information related to each other and having a dependency on the update order of the first information of each other;
The control program causes the processor to
Accepting an update to first information of any of the plurality of systems;
Accepting as the dependency relationship settings between the plurality of systems;
Determining an update order of each piece of first information held in the plurality of systems based on the dependency and the contents of the update when the update is received;
And updating the respective pieces of first information stored in the plurality of systems in the update order.

Images