JP2002373101A - Inter-directory cooperative method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an inter-directory cooperative method capable of shortening a processing time for completing processing within a time required for synchronization being requirements on a system operation in an information system for synchronizing a large amount of data in a batch at a fixed interval such as dates from a basic DB to the directories of in-system various synchronizing systems such as an enterprise information system. SOLUTION: Synchronization processing from a basic DB 150 to an information directory 120 and a load distribution directory 100 is paralleled, and the necessary data of different kinds of directories 130 being the destination of synchronization are extracted, and the synchronization processing is executed in advance. Even when there are a plurality of servers being the originals of the data, the matching of the preceding synchronizing data is managed by the load distribution directory 100 so that the matching can be guaranteed. Afterwards, the synchronization processing of the delayed synchronizable data from the information directory 120 to the different kinds of directories 130 is executed.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an inter-directory cooperation method for realizing data synchronization between different types of directories in an information system, and more particularly, to managing an original data in a main DB and storing information based on the data. The present invention relates to an inter-directory cooperation method for performing data synchronization processing to another heterogeneous directory in a system.

[0002]

2. Description of the Related Art In a large-scale information system such as a corporate information system, a directory system is widely used to manage organizational data of a company or personnel data of employees, and to store and share business-related information. Have been.

For example, it is used as a so-called electronic telephone directory function for retrieving a mail address from the first and last names of an e-mail transmission partner.

The directory system expresses information to be managed, such as people, organizations, and network devices, in a tree structure. This tree-structured data model is based on X.100, which is a CCITT recommendation, as a standard for directory systems. 50
0 (ISO9594).
Directory entries are arranged at locations corresponding to the branches and leaves of the tree structure, and serve as data units representing people and organizations. Each entry is a DN (Distinguis) which is a name indicating a path from the root of the directory tree.
hed Name). In addition, each entry is in addition to the user's email address,
Various information such as a first and last name, a user ID, a telephone number, and a password can be stored as attributes.

[0005] X. 500 defines the directory system as a client-server system,
The directory client can read and update the directory data by the DN, and can search using the attribute which is the data of the directory entry as a key. As a communication protocol between the client and the server used for reading, updating, and searching for this data, O
SI (Open Systems Interconne)
ction) based on the 7-layer model
repository Access Protocol). However, since DAP is a heavy-duty protocol that requires an OSI stack, its use has been frustrated.

Therefore, LDAP (Lightweight) is used as a lighter directory access protocol.
t Directory Access Protocol
ol) (RFC2251). LDAP is D
It is a subset of AP, runs on the TCP / IP stack, and is an Internet standards body, IETF (In
ternet Engineering Task Fo
(rce).

[0007] Incidentally, in recent corporate information systems, various applications such as an electronic mail system, a network OS, and groupware are introduced as needed in order to cope with diversification of business. However, these applications generally manage data such as user information and organization information in a separate DB, that is, in a separate directory. These directories often have different data structures to be managed. For this reason, the system administrator must manage all the directory data in the information system every time data update such as personnel changes or organizational reorganization is necessary, and the increase in the operational load has been a problem. .

[0008] For example, a backbone D for managing personnel data and the like
There are many duplicate attributes in the data managed by each directory in the information system, such as the management of employee names and user IDs in both the system B and the schedule management system, but many of the directories that manage these attributes At present, it is managed in a unique format using a unique database.

[0009] Therefore, there has been an issue of increasing the speed of data synchronization processing in order to reduce the management load of data synchronization processing between different types of directories and to cope with an increase in the amount of data to be processed due to an increase in the scale of an information system. .

As a prior art for solving the problem relating to such a heterogeneous directory cooperation method, Japanese Patent Laid-Open No. 11-83 is disclosed.
660 publication.

In the conventional technique, a directory synchronization server is provided between directories to be synchronized for directory synchronization, and the server manages a snapshot of an update source directory server. The update history performed on the directory server is periodically acquired, the acquired update history is sequentially referred to, the snapshot of the directory server is sequentially updated, and the content of the update history and the information of the snapshot are used. The type of update to the heterogeneous directory to be synchronized is determined, the content of the update history is converted into the schema of the heterogeneous directory, and the data is synchronized.

According to the synchronization method, even when the number of entries managed by the directory server increases, the time required for data synchronization between directories can be kept constant.

[0013]

However, in the above-mentioned inter-directory cooperation method, the increase in the time required for data synchronization processing between directories is kept constant irrespective of the increase in the number of entries registered in the directories. Was possible, but in a system where a large amount of data was updated in a batch, the processing of the update history could not be distributed by sequential processing and required for synchronous processing of a large amount of data. Also requires processing time.

For example, in FIG. 2, a directory server exists as an information directory 120 in the company information system, and manages all necessary data using this as a basis for in-house information. The user can obtain necessary information by referring to the information directory 120 when there is information such as an e-mail address and a telephone number to be obtained.

The core DB 150 stores the existing personnel D in the company.
B, etc., which is the original of the data in the information system.
The data in the information directory 120 is data synchronized based on the data in the main DB 150. However, since there are data that are not generally managed in the personnel DB and the like, such as the password of the information system, the data managed by the information directory 120 is the original of such data. Regarding the data for which the information directory 120 manages the originals, the administrator or the user operates the management terminal 1.
The management of data is performed via 40.

Further, there are systems that provide various functions in the enterprise information system. There are a mail system and a schedule management system. In such a system, data is generally managed independently, and each directory manages data that requires an individual directory. However, the data to be managed is managed such that the data consistency is ensured in the information system by synchronizing from the information directory 120.

Here, when synchronizing the data of the core DB, which is the original of the data in the information system, collectively with the directory system, generally, a time period during which the load on the information system is small due to nighttime batch processing or the like. However, at this time, data processing takes time in a large-scale system with a very large amount of data managed by the core DB, and the system operation requirements It has been difficult to complete the synchronization process within a certain period of time.

An object of the present invention is to perform a series of data synchronization from a core DB to a directory in an information system in an environment where a plurality of directory systems are operating in a large-scale information system such as an enterprise information system. The goal is to realize a method of linking directories that process at high speed.

[0019]

In order to achieve the above object, the present invention provides an information system for synchronizing data between a plurality of directories, and in particular, a large amount of information from a backbone DB to various information systems to be synchronized. In the information system that synchronizes the data, the processing paths are distributed according to the necessity of the data in the synchronization destination directory, and a new load distribution directory that manages the data to be synchronized with priority is newly provided to parallelize the synchronization processing. In addition, the present invention also provides a directory cooperation method for performing high-speed data synchronization by giving priority to synchronization processing of required data which is synchronization via a load distribution directory.

By using the inter-directory cooperation method, data required by each directory to be synchronized is set in advance, and the load balancing directory is used for synchronous data to be given priority in parallel with the normal path synchronization processing. , Necessary data is first synchronized with each directory, and the processing time of directory synchronization is reduced.

Further, according to the present invention, in executing the above-mentioned synchronization method, in an information system in which the data management of the original is managed by the information directory without the management of the main DB, the data of the data at the time of data synchronization by a plurality of paths is updated. Provide an inter-directory linkage method that guarantees consistency.

By using the inter-directory cooperation method, even in an information system in which original data in the information system is distributed in a plurality of directories, a synchronization process that guarantees data consistency between directories is realized. It becomes possible to provide an inter-directory cooperation method.

[0023]

Embodiments of the present invention will be described below in detail with reference to the drawings. In the following figure,
The same parts are given the same reference numerals.

FIG. 1 is a diagram showing the flow of a data synchronization process using the inter-directory cooperation method for realizing the present invention.

The backbone DB 50 is located in the enterprise information system.
For example, it is a DB for managing personnel data and the like, and the data managed by the core DB 50 is an original of data in the enterprise information system. The data update to the core DB 50 is collectively synchronized with another directory in the information system for a certain period of time defined as an operation requirement such as once every three days or the like.

The information directory 20 is a directory for managing data, such as employee information and organization information, used by the user in daily work. The data managed by the information directory 20 becomes an original as directory data, and based on the data, synchronizes the data with the heterogeneous directory 30 of various systems. If there is a data item that is not managed by the personnel DB, the information directory 20
Becomes the original, and in the synchronization processing between directories, the synchronization data is transferred to the load balancing directory 1.
Send to 0.

The heterogeneous directory 30 is a mail system that synchronizes with the information directory, an application server such as a schedule management system, and the like.
Generally, an information directory is a heterogeneous directory having a different data structure. The heterogeneous directory 30 independently manages data necessary for processing in its own server, but the data to be managed is data synchronized from the information directory.

The management terminal 40 is a client for updating data in the information directory, and a user or an administrator updates data from the management terminal 40. However, data to be updated from the management terminal 40 is limited to data not managed by the core DB 50.

The load distribution directory 10 is stored in the main DB 5
This is a directory for speeding up a synchronization process between a series of directories from 0 to a different directory 30. The load balancing directory 10 is a directory server that enables the heterogeneous directory 30 to manage only the minimum data required for processing of each server, thereby shortening the processing time in directory synchronization. In parallel with the synchronization process, the synchronization process from the core DB 50 to the load distribution directory 10 is performed.

At the time of inter-directory synchronization, the load balancing directory 1 is preceded by normal data synchronization processing.
0 is synchronized with the heterogeneous directory 30. Thereafter, if there is data to be synchronized from the information directory 20 to the heterogeneous directory 30, a synchronization process is performed.

By performing a series of synchronization processes between directories as described above, the processing time can be reduced. This embodiment is an inter-directory cooperation system that realizes a series of data synchronization as shown in FIG.

FIG. 3 is a functional configuration diagram of an inter-directory cooperation system for realizing the present invention.

The load distribution directory server 100 and the information directory server 2 are transmitted by a transmission medium 20 such as a LAN.
0, core DB server 150, heterogeneous directory server 1
30 are connected.

The load distribution directory server 100 stores data to be managed in the DB 50, and the information directory server 120 stores data to be managed in the DB 55. Further, the core DB 150 manages data to be managed in the DB 60, and the heterogeneous directory server 130 stores data necessary for unique processing in the DB 70.

The load distribution directory 100 is a key database.
150, information directory 120, heterogeneous directory 1
A communication control unit 30 that executes a communication process with the communication control unit 30; a synchronization setting management table 300 that stores settings related to a synchronization method;
DB control unit 2 that updates DB 50 according to the contents of the processing
5. Synchronization consistency management unit 1 that guarantees consistency of synchronization processing in response to data synchronization requests from a plurality of servers, schema conversion unit 3 that converts a data structure to generate data synchronized with heterogeneous directory server 130 And a synchronization control unit 2 for notifying the communication control unit 30 of the synchronization data in order to synchronize the converted data.

The information directory is, like the load distribution directory 100, a communication control unit 30, a DB 55, a DB control unit 25, a schema conversion unit 3, and a synchronization setting management table 3.
00 and a synchronization control unit 3.

The present embodiment is an inter-directory cooperation system having a functional structure as shown in FIG. 3 and realizing data synchronization between directories.

FIG. 4 shows a system configuration of the inter-directory cooperation system of this embodiment.

The load distribution directory 100 includes a central processing unit CPU 34, a secondary storage medium (hereinafter referred to as a magnetic disk) 33 such as a hard disk, a main storage memory (hereinafter referred to as a main memory) 31, a data bus 32, a display device, and the like. Output device (hereinafter referred to as display) 3
5. Input devices (hereinafter, referred to as a keyboard 36 and a mouse 37).

The DB 50 in FIG. 4 stores data on the magnetic disk 33. In addition, the synchronization consistency management table 20
0, the synchronization setting management table 300 is similarly stored on the magnetic disk 33.

The main memory 31 has a communication control unit 30, a synchronization control unit 2, a synchronization consistency management unit 1, a schema conversion unit 3, a DB
The control unit 25 is stored. These functions are stored in the magnetic disk 33 as programs, and are transferred to the main memory 31 as needed, and then executed by the CPU 34.

Next, the synchronization setting management table 300 and the synchronization consistency management table 200 according to the present embodiment will be described with reference to FIGS.

The synchronization setting management table 300 includes a backbone DB.
This is a table for storing settings relating to the method of synchronization from 150 to the heterogeneous directory 130, and comprises a synchronization server management table 310 and a synchronization attribute management table 220.

The synchronization server management table 310 is a table for setting the type of the heterogeneous directory 130 to be synchronized and the server ID used for the synchronization processing.
1 and two areas for storing the identification ID 312. The synchronization server 311 stores data such as the type of the application of the heterogeneous directory 130 and the name thereof, and the server ID 312 stores a unique integer value for enabling identification of the server when referring to the setting in the synchronization processing. Is done.

The synchronization attribute management table 320 is a table for setting the type of the attribute, the type of server to be synchronized, and the synchronization timing for each server for the attributes of the data stored in the DB 50 of the load distribution directory 100.
Each record of the synchronization attribute management table 320 includes a synchronization attribute type 321, a server ID 322, and a synchronization method 323. In the synchronization attribute type 321, an attribute required for the directory 130 to perform system processing is set. For example, name, mail address, password, and the like. The server ID 322 includes a synchronization attribute type 321
The server ID to be synchronized is set for the attribute set in. The server ID to be set can be selected only from the values set in the server ID 322 in the synchronous server management table 310. The synchronization method 323 specifies the server ID3 for the attribute set in the synchronization attribute type 321.
The item for setting the synchronization timing at the time of occurrence of the synchronization process corresponding to the server to be synchronized set in 22.

Next, a flow of a series of data synchronization processing from the main DB 150 to the heterogeneous directory 130 by daily synchronization in this embodiment will be described with reference to FIG.

FIG. 11 shows a process performed when a process of synchronizing the update of data registered in the core DB 150 with the information directory 120, the load distribution directory 100, and the heterogeneous directory 130 on a daily basis in the inter-directory cooperation system. It is a sequence.

When the daily synchronization set in the backbone DB 150 occurs, daily synchronization requests 81 and 82 are issued in parallel to the load distribution directory 100 and the information directory 120 in a batch of update data for one day.

The load distribution directory 100 and the information directory 120 store the synchronization request 8 from the main DB 150.
Upon receiving 1, 82, each directory reflects the synchronization data after returning daily synchronization responses 83, 84, respectively.

The information directory 120 is stored in the main DB 15
If there is data that is not managed by 0 and managed by the own directory as the original data of the data, a preceding synchronization data reflection request 85 is transmitted to the load distribution directory 100 to synchronize the data.

Upon receiving the preceding synchronization data reflection request 85 from the information directory 120, the load distribution directory 100 performs consistency management with the daily update data received in the daily synchronization request 81 from the main DB 150, and then Synchronous data to the heterogeneous directory 130 is generated.

After generating the synchronization data, a synchronization request 86 is issued to the heterogeneous directory 130, and the heterogeneous directory 1 is
Numeral 30 returns a synchronization response 87 to the load distribution directory 100 when the synchronization data is normally received, and reflects the synchronization data.

Upon receiving the synchronization response 87, the load distribution directory 100 returns a preceding synchronization data reflection response 88 to the information directory 120.

After receiving the response 88, the information directory 120 issues a daily synchronization request 89 for the data to be synchronized with the heterogeneous directory 130, and the heterogeneous directory 130 reflects the synchronization data after receiving the request 89. , Returns a daily synchronization response 90 to the information directory 120.

At this time, in the logs of the heterogeneous directory 130, the synchronization request 86 from the load distribution directory 100 and the daily synchronization request 89 from the information directory 120
When the request is received and the DB 70 is updated, it can be confirmed that the record has been written to the log. On the other hand, in the information directory 120 and the load distribution directory 100, the daily synchronization requests 81 and 83 are received as synchronization requests from the core DB.
By referring to the logs, the two synchronization requests 81, 8
It can be seen that 3 was processed in parallel.

Therefore, by referring to these logs, in a series of processes for daily synchronization of updates to the core DB 150 with another directory, two synchronization requests 81,
Regarding 83, it is apparent that processing is performed in parallel with the execution of the daily synchronization, and in the heterogeneous directory 130, the synchronization request 86 is reflected as synchronization data prior to the daily synchronization request 89, and the data is updated in the DB 70. It is.

The application of the present invention is clear from the fact that the functions provided by the present embodiment are generally described in manuals and the like for products and the like.

The operation of the inter-directory cooperation system according to this embodiment will be described below.

FIG. 7 is a flowchart showing an operation related to the inter-directory synchronization process from the main DB 150 to the different directory 130, which is performed based on the schedule set in the present system.

More specifically, the synchronizing process from the main DB 150 to the load balancing directory 100 and the information directory 120 and the synchronizing process from the information directory 120 to the load balancing directory 100 and the heterogeneous directory 130 are shown. The two methods of synchronizing between directories are almost the same except for a part of the processing, and the different parts will be described in the following description of the drawings.

In the inter-directory synchronization process, when a preset synchronization condition is satisfied, the synchronization process is performed from the main DB 150 to the heterogeneous directory 130. As the inter-directory synchronization condition, for example, the following condition can be set. (1) Time conditions. This is a condition for executing synchronization every predetermined time unit such as hour, day, week, month, and year. For example, a condition setting such that synchronization processing is started at 22:00 on every Sunday is cited. (2) Data volume. Conditions include, for example, when the number of records of the update data in the core DB becomes a certain number or more, or when the file size of the update log becomes a certain size or more.
The synchronization conditions that can be set are expandable, and can be applied to conditions other than the above two conditions.

The main DB 150 monitors whether or not the synchronization condition is satisfied in step S401, and when it is determined that the synchronization setting condition is satisfied, acquires update data to be synchronized in step S402.

Next, in step S403, the synchronization setting management table is read.

In step S404, step S404
In step S405, it is determined whether or not the read data is preceding synchronization data, and the subsequent processing is branched according to the determination result.

The result of the determination in step S404 is
If it is the preceding synchronization data, data for synchronization is generated as the preceding synchronization data in step S406.

Next, in step S407, the generated synchronization data is subjected to schema conversion so that the load distribution directory can be updated.

In step S408, step S408
In 407, the synchronization data, which is the result of the schema conversion, is transmitted to the load distribution directory 100.

Upon receiving the synchronous data, the load distribution directory 100 executes the preceding data entrainment processing in step S409.

On the other hand, if it is determined in step S405 that the data is not the preceding synchronous data, the process proceeds to step S4
In step 10, it is determined whether or not the data is general synchronous data. If the data is not general synchronous data, the data is not data to be synchronized. Therefore, in step S415, the data update information is discarded.

If it is determined in step S410 that the data is general synchronous data, in step S411, the data is generated as synchronous data using the data as general synchronous data.

Next, in step S412, the generated data for synchronization is subjected to schema conversion processing in accordance with the schema of the directory to be updated.

Here, from the information directory 120 to the load distribution directory 100 and the heterogeneous directory 130
In synchronization with the information directory 120, the information directory 120 synchronizes from the information directory 120 to the heterogeneous directory 130 after the preceding data synchronization processing from the load distribution directory 100 to the heterogeneous directory 130 is completed.

For this reason, it is determined in step S 413 whether or not a preceding data synchronization completion notification has been received from the load distribution directory 100. If the preceding data synchronization processing has already been completed, in step S 414, the process proceeds to step S 414. Perform synchronous processing.

In the synchronization from the core DB 150 to the load distribution directory 100 and the information directory 120, no determination regarding the completion of the preceding data synchronization processing is performed.
The synchronization processing to the information directory 120 is performed as it is.

FIG. 8 shows the preceding data synchronization processing (S4 in FIG. 7).
It is a flowchart showing operation | movement of 04).

First, in step S501, the load distribution directory 100 reflects the synchronization data received in the data synchronization request from the main DB 150 in the DB 50.

Next, in step S502, directory synchronization data generation processing is performed by the synchronization consistency management unit 1, the synchronization control unit 2, and the schema conversion unit 3.

Based on the synchronization data generated in step S502, the synchronization control unit 2 executes a synchronization process on the heterogeneous directory 130 in step S503.

FIG. 9 is a flowchart showing the operation of the directory synchronization data generation process (S502 in FIG. 8).

First, in step S601, the synchronization coordination management unit 1 of the load distribution directory 100 reads the synchronization setting management table 300, and extracts the data to be synchronized received from the main DB 150 in step S602.

Next, in step S603, a synchronization consistency management process is executed.

After the above series of processing is completed, step S604
The schema conversion unit 3 performs a schema conversion process so that the data to be synchronized can be synchronized with the heterogeneous directory 130 in.

Finally, in step S605, S60
It is determined whether or not the synchronization data has been generated for all the synchronization target directories based on the settings of the synchronization setting management table 300 read in 1. If there is a synchronization directory for which no synchronization data has been generated yet, , S602
To repeatedly execute a series of synchronous data generation processing.

FIG. 10 shows the synchronization consistency management process (S6 in FIG. 9).
It is a flowchart showing operation | movement of 04).

First, in step S701, S6
Based on the settings of the synchronization consistency management table 200 read in step 01, it is determined whether or not it is necessary to receive preceding synchronization data from the information directory 120.

If it is determined that synchronous data must be received from the information directory 120, step S70
In 2, it is determined whether or not data has been received.

At S702, the information directory 120
If it is determined that the synchronization data from has not been received yet, the process waits until data is received.

On the other hand, if the reception of the synchronous data is confirmed in S702, the synchronous data from the information directory 120 is obtained in step S703.

Next, in step S704, the key D
Synchronous data received from B150 and information directory 1
It is determined whether or not there is an update for the same entry with the synchronous data received from 20.

If the result of determination is that updates to the same entry have been received as synchronous data, step S705
In, the process branches based on the synchronous data update type.

If it is determined in step S705 that the entry is to be deleted, the process proceeds to step S706.
The update request recorded in the synchronization data received from the information directory 120 of the entry is discarded.

As for the synchronous data having no relation between the entries, the data is combined in step S707.

On the other hand, if it is determined in S705 that there is no deletion request for the same entry, in step S708, the synchronization data is combined in a time series such that the synchronization request of the main DB 150 is processed after the synchronization request of the information directory 120. I do.

If it is determined in S704 that there is no update request for the same entry, the update data in the main DB 150 and the synchronization data in the information directory 120 are combined in step S709, and
If it is determined in 1 that there is no need to receive synchronous data from the information directory 120, the process ends without performing any processing.

The first embodiment of the inter-directory cooperation method of the present invention has been described above. According to this inter-directory cooperation method, when data is synchronized from the core DB to the directory of another system in the enterprise information system, the necessity of writing the update attribute is determined, the synchronization process is parallelized, and the synchronization process is performed from a plurality of synchronization paths. By managing the update consistency, it is possible to provide a function of processing a series of synchronization processes from the core DB to the synchronization system at high speed while ensuring the consistency.

[0096]

As described above, according to the present invention, in data synchronization processing between directories in an information system, synchronization timing is set based on attributes required for each directory to be managed, and data update processing is performed. By associating the objects and attributes, which are the update contents, when the system occurs, it is possible to perform data management that guarantees consistency regardless of the difference in synchronization timing. As a result, a series of synchronization processes can be completed within the restrictions on the operation of the information system, such as synchronizing the update data in the information system all at once within a certain time at night.

[0097]

[Brief description of the drawings]

FIG. 1 is a system schematic diagram of an inter-directory cooperation method of the present invention.

FIG. 2 is a system schematic diagram of an existing inter-directory cooperation method.

FIG. 3 is a functional configuration diagram of the first embodiment of the present invention.

FIG. 4 is a system configuration diagram of the first embodiment of the present invention.

FIG. 5 is a data structure diagram of a synchronization setting management table of the present invention.

FIG. 6 is a data structure diagram of a synchronization consistency management table of the present invention.

FIG. 7 is an explanatory diagram of an operation related to an inter-directory synchronization process according to the embodiment of this invention.

FIG. 8 is an explanatory diagram of an operation related to a preceding data synchronization process according to the embodiment of this invention.

FIG. 9 is an explanatory diagram of an operation related to directory synchronization data generation processing according to the embodiment of this invention.

FIG. 10 is an explanatory diagram of an operation related to a synchronization consistency management process according to the embodiment of this invention.

FIG. 11 is a processing sequence diagram in a daily synchronization process according to the embodiment of the present invention.

DESCRIPTION OF SYMBOLS 1 ... Synchronization consistency management unit, 2 ... Synchronization control unit, 3 ... Schema conversion unit, 100 ... Load distribution directory, 120 ... Information directory, 130 ... Heterogeneous directory, 150 ... Core DB, 200 ... Synchronization consistency management Table, 300: Synchronization setting management table.

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Masaya Kono 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture F-term in Platform Solutions Development Division, Hitachi, Ltd. F-term (reference) 5B075 KK03 KK07 NK43 NR06 NR20 5B082 HA03

Claims (3)

[Claims] 1. There is at least one server that manages data required for processing in a unique format, and among the servers, data managed by a server that handles original data of data can be used for various purposes. Therefore, in an information system having a function of collectively synchronizing with a directory of at least one or more other systems at regular intervals, a load balancing directory for managing data necessary for operation of each system in addition to the collective synchronization function A method for inter-directory cooperation, comprising: means for performing a batch synchronization process of data in parallel by using a plurality of paths. 2. The inter-directory cooperation method according to claim 1, wherein an update result of the original data is converted into data that is required by each directory to be synchronized at a minimum and data that may be synchronized with a delay. A synchronization setting management table for discrimination is provided, in which each discrimination type is synchronized in parallel with another directory for each type of data, and data determined to be necessary in the discrimination is synchronized in advance of other data. A method of linking directories, comprising a synchronization control unit as means. 3. The inter-directory cooperation method according to claim 1, wherein a data update result in a server that manages a plurality of data originals existing in the information system is updated by a first server that manages the data originals. In response to a data synchronization request from a plurality of paths for synchronizing the update of the second server that manages the original data of which the first server does not manage the original data, the first server manages the update contents in chronological order. A synchronization consistency management table, which is means for performing synchronization while guaranteeing data consistency, and a synchronization consistency management unit.