JP2011141687A - Ldap directory data conversion program and device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce the labor of an operator when converting a plurality of CSV files having a hierarchical structure or a reference relation into data in an LDIF format. <P>SOLUTION: In an LDAP(Lightweight Directory Access Protocol) directory data conversion device 30, an input part 33 obtains each CSV file from a relational database device 10, and a data conversion part 35 converts an organization CSV file having hierarchical composition among CSV files transmitted from a control part 34 into first data in an LDIF format in which organization names are arranged in the order of organization ID based on host organization ID according to hierarchical composition definition information, and converts a user CSV file having a reference relation into second data in an LDIF format in which user names are arranged for each user ID according to reference relation definition information, and creates third data in an LDIF format by writing the second data after the first data, and an output part 36 outputs the third data to an LDAP directory device 20 as one LDIF file. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to an LDAP directory data conversion technique for converting data in a table format stored in a relational database into data in an LDAP Data Interchange Format (LDIF) format, which is an LDAP (Lightweight Directory Access Protocol) data exchange format.

  Currently, there are relational databases and LDAP (Lightweight Directory Access Protocol) directories as commonly used databases. In a relational database, all data is stored in a two-dimensional table format consisting of rows and columns. Also, unlike the relational database, the LDAP directory stores data in a tree format called DIT (Directory Information Tree).

  In addition, the relational database and the LDAP directory differ in the presence or absence of standardization of the data structure and access method. Relational databases are not standardized because the data structure and access method are uniquely determined by the database designer, and basically cannot be used by those who do not know the specifications of the data structure and access method. On the other hand, in the LDAP directory, since the data structure and the access method are standardized in the specifications of X.500 and LDAP, they can be easily used if they comply with this specification.

  In addition, the relational database has transaction control defined, and has an advantage suitable for a large amount of data update processing. On the other hand, since the transaction control is not clearly defined in the LDAP directory, it is unsuitable for updating a large amount of data, but has an advantage of excellent search performance for a large amount of data.

  Because of these differences, the relational database and the LDAP directory are properly used in the right place according to the nature and use of the data. In particular, the LDAP directory has a standardized access method and excellent search performance, and stores data in a tree format suitable for representing the organizational hierarchy of a company. The number of cases used as an integrated ID management server is increasing. For example, there is an increasing number of cases where a relational database is transferred to an LDAP directory with the introduction of an authentication server for an in-house system or integration of IDs.

  In such migration, it is necessary to convert table format data stored in a relational database into tree format data in the LDAP directory. Such data conversion is executed by the following procedures (1) to (4) (for example, see Non-Patent Document 1).

(1) Create a CSV file for each table.
(2) Create a schema mapping definition file for each CSV file. The schema mapping definition file is a file in which a generation rule for generating an LDIF file from a CSV file is defined.
(3) Convert the CSV file into an LDIF file according to the generation rule described in the schema mapping definition file.
(4) Import the LDIF file into the LDAP directory.

That is, as shown in FIG. 14, the conversion tool 1 converts the individual CSV files 2 ₁ , 2 ₂ ,..., 2 _n created for each table in the relational database device 10 into schema mapping definition files 3 ₁ , 3 _2. , ..., each LDIF file ₄ 1 in accordance with _{3 n,} 4 2, ..., is converted into one-to-one to _{4 n,} each LDIF file _{4 1,} 4 2, ..., LDAP directory in consideration of the order relation of _{4 n} Import to device 20.

Hitachi, Ltd. LDAP Toolkit (Example of using LDAP Toolkit CSV converter), URL: http://www.hitachi.co.jp/Prod/comp/soft1/sjs/product/lineup/pdf/ldap_use.pdf

However, in the data conversion method as described above, for the plurality of CSV files 2 ₁ , 2 ₂ ,..., 2 _n having a hierarchical structure and a plurality of data having a reference relationship between the tables, the LDAP conversion method is used. taking into account the relationship between hierarchy and entry, the schema mapping definition worker file 3 _1, 3 2, _..., it is necessary to create each 3 _n. Since the creation of such schema mapping definition files 3 ₁ , 3 ₂ ,..., 3 _n places a heavy burden on the operator, it is desirable to reduce the burden.

  The present invention has been made in consideration of the above circumstances, and an LDAP directory data conversion program capable of reducing the burden on an operator when converting a plurality of CSV files having a hierarchical structure or a reference relationship into LDIF format data, and An object is to provide an apparatus.

  In one aspect of the present invention, a table format in which a set name item having a set name as a value and a higher set ID item having a higher set ID as a value is associated with each set ID item having a set ID as a value. Storing the set information, the element name item having the element name as the value for each element ID item having the element ID as a value, and the element information in a table format in which the allocation set ID item having the allocation set ID as a value is associated with each other, When receiving a LDIF file, a relational database device capable of outputting each CSV file composed of a set CSV file obtained by converting set information into CSV format, and an element CSV file obtained by converting the element information into CSV format. The LDAP directory device is capable of communicating with each LDAP directory device to be imported and has storage means. An LDAP directory data conversion program for use in a data conversion device, wherein the LDAP directory data conversion device includes a hierarchical item having a set ID item as a value and an upper set ID item as a value for each file name of the set CSV file. Means for writing the hierarchical structure definition information associated with the upper hierarchy definition items held in the storage means, and for each file name of each CSV file, a reference destination CSV file name or a reference destination CSV name having a non-applicable value; Means for writing reference relationship definition information associating a reference source item having a reference source assigned set ID item or an irrelevant value and a reference destination item having a reference destination set ID item or an irrelevant value into the storage unit , An acquisition means for acquiring each CSV file from the relational database device; That is, an unconverted file sending means for individually sending unconverted CSV files, and when the sent CSV file is a set CSV file having a hierarchical structure, the set CSV file is determined based on the hierarchical structure definition information. First data conversion means for converting to LDIF format first data in which set names are arranged in the set ID order based on the higher set ID, and when the sent CSV file is an element CSV file having a reference relationship, this element CSV file Based on the reference relationship definition information, second data conversion means for converting to LDIF format second data in which element names are arranged for each element ID, and the second data to be continued after the first data LDIF data creation means for writing and creating third data in LDIF format, and sending the third data that has been created An LDAP directory data conversion program for functioning as creation completion data sending means and output means for outputting the sent third data as one LDIF file to the LDAP directory apparatus.

  Although one aspect of the present invention is expressed as a program, the present invention is not limited thereto, and may be expressed as a computer-readable storage medium storing an apparatus, a method, or a program.

(Function)
In one aspect of the present invention, when a plurality of CSV files having a hierarchical structure or a reference relationship are converted into LDIF format data, the conversion is performed based on the hierarchical configuration definition information and the reference relationship definition information. The trouble of creating the schema mapping definition file can be eliminated, and the burden on the operator can be reduced.

  As described above, according to the present invention, when a plurality of CSV files having a hierarchical structure or a reference relationship are converted into LDIF format data, the burden on the operator can be reduced.

1 is a schematic diagram illustrating a configuration of an LDAP directory data conversion system including an LDAP directory data conversion apparatus according to an embodiment of the present invention. It is a schematic diagram for demonstrating each data in the table storage part in the embodiment. It is a schematic diagram for demonstrating the LDAP hierarchical structure data in the data storage part in the embodiment. It is a schematic diagram for demonstrating the LDIF file in the same embodiment. It is a schematic diagram for demonstrating each data in the rule definition part in the embodiment. It is a schematic diagram for demonstrating the CSV process management information in the CSV process management part in the embodiment. It is a flowchart for demonstrating the operation | movement in the embodiment. It is a schematic diagram for demonstrating operation | movement of step S0 in the same embodiment. It is a schematic diagram for demonstrating operation | movement of step S6 in the same embodiment. It is a schematic diagram for demonstrating the creation operation of the LDIF file in the embodiment. It is a schematic diagram for demonstrating the update operation | movement of CSV process management information in the embodiment. It is a schematic diagram for demonstrating operation | movement of step S9 in the same embodiment. It is a schematic diagram for demonstrating the effect of the same embodiment. It is a schematic diagram which shows the conventional LDAP directory data conversion method.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The following LDAP directory data conversion apparatus can be implemented with either a hardware configuration or a combined configuration of hardware resources and software. As the software of the combined configuration, a program that is installed in advance from a network or a storage medium into a computer that becomes an LDAP directory data conversion device and causes the computer to realize the function of the LDAP directory data conversion device is used. In the following embodiment, “organization” is used as a specific example of “set” having a hierarchical structure, “user” is used as a specific example of “element” in the set, and “assignment” of elements to the set is set. Although “affiliation” is used as a specific example, specific examples of “aggregation”, “element”, and “assignment” are not limited to organizations, users, and affiliations, and arbitrary ones can be used. For example, “field” may be used as another specific example of “set”, “document” may be used as a specific example of element, and “classification” may be used as a specific example of “assignment”.

(One embodiment)
FIG. 1 is a schematic diagram showing a configuration of an LDAP directory data conversion system provided with an LDAP directory data conversion apparatus according to an embodiment of the present invention, and FIGS. 2 to 6 are schematic diagrams for explaining each data and the like. is there. The LDAP directory data conversion system includes a relational database device 10, an LDAP directory device 20, and an LDAP directory data conversion device 30.

  Here, the relational database device 10 includes a table storage unit 11 and a CSV output unit 12.

  As shown in FIG. 2, the table storage unit 11 includes a storage device that stores a user table definition 11a, an organization master table definition 11b, user master data 11c, and organization master data 11d. Accordingly, the data 11a to 11d are written and can be read from the CSV output unit 12.

  The user table definition 11a is user information definition information that defines the data item (physical name) of the user master data 11c. For each row number, the attribute name, physical name, PK (whether or not it is a primary key), and FK (external) Data item is defined. As the attribute name, a user ID, a user name, a belonging organization, an email, and a telephone number are defined. USER_ID, USER_NAME, SYOZOKU, MAIL, and TEL are defined as physical names. The primary key is defined as USER_ID and SYOZOKU is defined as a foreign key for sosiki.csv.

  The organization master table definition 11b is organization information definition information that defines data items (physical names) of the organization master data 11c. For each row number, the attribute name, physical name, PK (whether or not it is a primary key), and FK ( Data item is defined. As the attribute name, an organization ID, an organization name, a telephone number, and an upper organization are defined. ORG_ID, ORG_NAME, ORG_TEL, and HIGH_ORG_ID are defined as physical names. Primary key is defined as ORG_ID and HIGH_ORG_ID is defined as foreign key of sosiki.csv itself. HIGH_ORG_ID has a recursive structure and represents the hierarchical structure of the organization.

The user master data 11c includes a user name item having a user name (eg, Ichiro Tanaka, Jiro Sato,...) As a value for each USER_ID as a user ID item having a user ID (eg, 00001, 00002,...) As a value. Table format that associates USER_NAME as, belonging organization ID item (eg, A01, B01, ...) as a belonging organization ID item, MAIL (mail) and TEL (telephone number) as optional additional items And is output as a user CSV file (user.csv) 2 ₁ converted into the CSV format by the CSV output unit 12.

The organization master data 11d includes an organization name item having an organization name (eg, organization A01, organization B01,...) As a value for each ORG_ID as an organization ID item having an organization ID (eg, A01, B01,...) As a value. ORG_NAME as an optional information, ORG_TEL (organization telephone number) as an optional additional item, and organization information (aggregate information) in a table format in association with HIGH_ORG_ID as an upper organization ID item having a higher organization ID as a value, and a CSV output unit 12 by output as a tissue CSV file (sosiki.csv) _{2 2} converted into CSV format.

CSV output unit 12, the table storage unit and the user CSV file _{2 1} user master data 11c was converted into CSV format 11, tissue CSV file tissue master data 11d was converted to CSV format in the table storage unit 11 _{2 2} The CSV file 2 ₁ , 2 ₂ having the following functions is output to the LDAP directory data converter 30. Here, each output CSV file (user.csv, sosiki.csv) 2 ₁ , 2 ₂ has a one-to-one correspondence with each master data 11c, 11d, and the same number as the number of master data 11c, 11d. CSV files 2 ₁ and 2 ₂ are output.

  The LDAP directory device 20 includes a data storage unit 21 and an LDIF input unit 22.

  As shown in FIG. 3, the data storage unit 21 is composed of a storage device that stores LDAP hierarchical structure data. The LDAP hierarchical structure data is written from the LDIF input unit 22, and the reading unit (not shown) performs the LDAP hierarchical structure according to a user operation. The structure data can be read out. Note that the LDAP hierarchical structure data is data in a tree format called DIT (Directory Information Tree). For this reason, the hierarchical structure may be called a tree structure. Further, the hierarchical structure may be called a directory structure.

When the LDIF input unit 22 receives the LDIF file 4 output from the LDAP directory data conversion device 30, the LDIF input unit 22 imports the LDAP file 4 and converts it into LDAP hierarchical structure data, and the LDAP hierarchical structure data is a data storage unit. 21 with the function to write. Here, LDIF file 4, as shown in FIG. 4, the first data 4 ₁ LDIF format formed by arranging the organizational data in hierarchical order, the LDIF format formed by arranging a user data associated with the organizational data first and a third data _{4 3} LDIF format and a second data _{4 2.} The third data 4 _3, since the second data 4 ₂ is written to continue after the first data 4 ₁ is created.

  The LDAP directory data conversion device 30 includes a rule definition unit 31, a CSV processing management unit 32, an input unit 33, a control unit 34, a data conversion unit 35, and an output unit 36.

  The rule definition unit 31 is a storage device that is readable / writable by the control unit 34, and as rule information that is defined so that CSV format data can be converted into LDIF format data, as shown in FIG. A definition 31a, an attribute mapping definition 31b, an arrangement configuration definition 31c, an entry relationship definition 31d, and a hierarchy configuration definition 31e are stored. Each definition 31a to 31e is written in the rule definition unit 31 by the control unit 34 in advance according to the operation of the input unit 33 by the user.

  In the object class mapping definition 31a, an object class of LDAP hierarchical structure data is associated with each CSV file name. In the example illustrated in FIG. 5, the CSV file name “user” is associated with the object class “top, inetOrgPerson, xxxPerson”, and the CSV file name “sosiki” is associated with the object class “top, organizationalUnit, xxxOrganization”. Here, the representations of the object classes are described by separating them from the top of the object class tree with commas, but other representations may be used. The object classes “xxxPerson” and “xxxOrganization” indicate object classes that are uniquely extended, and other object classes are LDAP standard object classes.

The attribute mapping definition 31b includes, for each CSV file name, CSV data (CSV attribute item) having the physical names in the CSV files 2 ₁ and 2 ₂ as values, and LDIF data (LDIF data having the physical names in the LDIF file 4 as values). Attribute item) and PK item (whether or not it is the primary key of the LDAP file). The part in which the physical name in the LDIF file 4 is represented by “− (minus)” indicates that the physical name in the CSV files 2 ₁ and 2 ₂ is not associated with the physical name in the LDIF file 4. I mean. In this example, the CSV file name physical name of the CSV file ₂ in ₁ "user", "SYOZOKU", the physical name of the CSV file ₂ in the _second CSV file name "sosiki" and "HIGH_ORG_ID", respectively associated LDIF file The physical name in “4” is “−” and is not associated with the physical name in the LDIF file 4, but these physical names “SYOZOKU” and “HIGH_ORG_ID” are the hierarchies in the LDAP hierarchical structure data. It will be expressed in the relationship.

  The arrangement configuration definition 31c is information defining a position (hereinafter also referred to as a tree point) at which LDAP hierarchical structure data is written. In this example, it is defined that the tree point is “o = xxx.co.jp”.

The entry relation definition 31d includes, for each CSV file 2 ₁ , 2 ₂ , a reference destination CSV file name or a reference destination CSV name having a non-applicable value, a reference source belonging organization ID item or a non-applicable value. Reference relationship definition information in which a reference source item and a reference destination item having a non-applicable value are associated with each other, and define an entry relationship (reference relationship) after conversion to the LDIF format It is. In this example, CSV file 2 ₁ of the file name in the "user", a reference destination CSV name with the referenced file name "sosiki", and see the original item with a reference source of the organization ID item "SYOZOKU", reference The reference destination item having the previous organization ID item “ORG_ID” is associated. In addition, to a CSV file 2 ₂ of the file name "sosiki", applicable without value reference with - a reference destination CSV name with the corresponding no value "" - - and see the original item with the corresponding no value ",""," Associated with the previous item. This reference relationship is converted into a hierarchical relationship in the LDAP hierarchical structure data. Specifically, entries of users belonging to the organization are arranged under the organization entry.

Hierarchy definition 31e, for each tissue CSV file _{2 2} File name (Sosiki), a hierarchical item with organization ID fields as an organization ID item (ORG_ID) the value, the upper layer ID field as level organization ID field ( HIGH_ORG_ID) is hierarchical configuration definition information associated with a higher hierarchy definition item having a value. Here, the “hierarchy item” designates a data item that represents a hierarchy, and here, ORG_ID that is an organization ID item is defined. The “upper hierarchy definition item” designates a data item indicating the upper hierarchy, and here, HIGH_ORG_ID which is an upper organization ID item is designated.

  Each of the definitions 31a to 31e in the rule definition unit 31 may use a notation different from the notation exemplified in the present embodiment.

The CSV process management unit 32 is a storage unit that is readable / writable from the control unit 34. As shown in FIG. 6, each CSV file 2 ₁ , 2 ₂ acquired from the relational database device 10 and the unprocessed status It has a function of storing CSV processing management information associated with a value.

The input unit 33 has a function of acquiring the CSV files 2 ₁ and 2 ₂ from the relational database device 10 and a function of transmitting the acquired CSV files 2 ₁ and 2 ₂ to the control unit 34.

Note that the functions of acquiring the CSV files 2 ₁ and 2 ₂ from the relational database device 10 include, for example, a function of transmitting an output request for each of the CSV files 2 ₁ and 2 ₂ to the relational database device 10 and from the relational database device 10. And a function of receiving input of a plurality of output CSV files 2 ₁ and 2 ₂ .

Further, when the input unit 33 receives the input of the CSV files 2 ₁ and 2 ₂ , the input unit 33 may perform a syntax check of the CSV data in the CSV files 2 ₁ and 2 ₂ .

The control unit 34 writes each CSV file 2 ₁ , 2 ₂ from the input unit 33 to the CSV process management unit 32, and each CSV file 2 ₁ , 2 ₂ in the CSV process management unit 32 and each in the rule definition unit 31. The definitions 31a to 31e are sent to the data conversion unit 35, the data converted by the data conversion unit 35 are sent to the output unit 36, and the CSV file processing status is sent to the CSV processing management unit 32 in the process of data conversion. To record. The control unit 34 also writes the definitions 31 a to 31 e received from the input unit 33 in the rule definition unit 31.

Such a control unit 34 has, for example, the following functions (f34-1) to (f34-4).
(f34-1) A function of writing CSV process management information in which each CSV file 2 ₁ , 2 ₂ acquired by the input unit 33 is associated with an unprocessed status value into the CSV process management unit 32.

(f34-2) An unconverted file transmission function for individually transmitting unconverted CSV files to the data conversion unit 35 among the CSV files 2 ₁ and 2 ₂ acquired by the input unit 33.

(f34-3) A function of updating the unprocessed status value of the CSV process management information to the processed status value in association with the converted CSV files 2 ₁ and 2 ₂ for each conversion of the data conversion unit 35.

(f34-4) Created data sending function for sending a third data 4 ₃ created by the data converting unit 35 is completed to the output unit 36.

  Here, the creation completion data transmission function (f34-4) may include the following functions (f34-4-1) to (f34-4-2).

(f34-4-1) A function of referring to the CSV process management information in the CSV process management unit 32 and determining whether or not all the CSV files 2 ₁ and 2 ₂ are associated with the processed status values.

(f34-4-2) the result of this determination, if all of the CSV files 2 ₁ in the CSV processing management _information, 2 ₂ are associated with the processed status value, the output unit 36 the third data 4 ₃ Function to send out.

  The unconverted file transmission function (f34-2) refers to the CSV process management information in the CSV process management unit 32 when the result of the determination by the determination function (f34-4-1) is negative. It may be realized as a function of individually sending a CSV file related to the unprocessed status value to the data conversion unit 35.

The data conversion unit 35 performs conversion from CSV format data to LDIF format data based on the CSV files 2 ₁ and 2 ₂ received from the control unit 34 and the definitions 31a to 31e in the rule definition unit 31. is there.

  Specifically, the data converter 35 has the following functions (f35-1) to (f35-3).

(f35-1) When the CSV file sent from the control unit 34 is an organization CSV file having a hierarchical structure, the organization CSV file is assigned organization names in order of organization ID based on the higher organization ID based on the hierarchical configuration definition 31e. first data conversion function for converting the first data _{4 1} arrangement the LDIF format.

(f35-2) When the CSV file sent from the control unit 34 is a user CSV file having a reference relationship, the user CSV file is an LDIF format in which a user name is arranged for each user ID based on the entry relationship definition 31d. second data conversion function for converting second data 4 _2.

(f35-3) LDIF data creation function for creating a third data _{4 3} LDIF format second data _{4 2} writes the to continue after the first data _{4 1.}

  Here, the first data conversion function (f35-1) may include the following functions (f35-1-1) to (f35-1-4).

  (f35-1-1) For the CSV file sent from the control unit 34 by the unconverted file sending function (f34-2), refer to the entry relation definition 31d in the rule definition unit 31, and the file of the CSV file A reference destination absence determination function for determining whether or not a reference destination CSV name related to a name has a non-applicable value.

  (f35-1-2) If the result of determination by the non-reference destination determination function (f35-1-1) is negative, the CSV file transmitted from the control unit 34 by the unconverted file transmission function (f34-2) On the other hand, referring to the CSV process management information in the CSV process management unit 32 and the entry relation definition 31d in the rule definition unit 31, the reference CSV file indicated by the reference CSV name related to the file name of the CSV file A reference destination processed determination function that determines whether a name is associated with a processed status value in CSV process management information.

  (f35-1-3) When the reference destination name has a non-applicable value as a result of determination by the reference destination absence determination function (f35-1-1), or the reference destination processed determination function (f35-1-2) When the reference CSV file name indicated by the reference CSV name is associated with the processed status value as a result of the determination by the above, the CSV file matches each value of the hierarchy configuration definition 31e in the rule definition unit 31 It is determined whether or not there is an organization ID item and an upper organization ID item to be selected, and as a result of this determination, an organization file selection for selecting a CSV file having an organization ID item and an upper organization ID item as an organization CSV file having a hierarchical structure function.

  The second data conversion function (f35-2) may include the following function (f35-2-1).

  (f35-2-1) As a result of the determination in the organization file selection function (f35-1-3), the entry relationship definition 31d in the rule definition unit 31 is defined for the CSV file having no organization ID item and higher organization ID item. User file selection that determines whether or not there is a belonging organization ID item that matches the value of the reference source item, and, as a result of this determination, selects a CSV file having the belonging organization ID item as a user CSV file having a reference relationship function.

The output unit 36 has a function of outputting to the LDAP directory device 20 a third data _{4 3} LDIF format received from the control unit 34 as one LDIF file 4.

  Next, the operation of the LDAP directory data conversion system configured as described above will be described with reference to the flowchart of FIG.

The LDAP directory data conversion apparatus 30 transmits an output request for each of the CSV files 2 ₁ and 2 ₂ to the relational database apparatus 10 by, for example, a user operation.

In a relational database system 10, based on the output request, CSV output unit 12, a user CSV file _{2 1} obtained by converting the user master data 11c in the table storage unit 11 in the CSV format, tissue master in the table storage unit 11 and it outputs the CSV file ₂ 1 comprising a data 11d from the transformed tissue CSV file _{2 2} which in CSV format, _{2 2} to the LDAP directory data converter 30.

(Step S 0) In the LDAP directory data conversion device 30, when the input unit 33 acquires the CSV files 2 ₁ and 2 ₂ , the input unit 33 sends the acquired CSV files 2 ₁ and 2 ₂ to the control unit 34. As shown in FIG. 8, the control unit 34 sets CSV process management information in which each CSV file (user.csv, sosiki.csv) 2 ₁ , 2 ₂ is associated with an unprocessed status value (N, N) as CSV. Write to the process management unit 32.

(Step S1) The control unit 34 refers to the CSV process management information in the CSV process management unit 32, and determines whether or not the processes of all the CSV files 2 ₁ and 2 ₂ have been completed. This determination is performed by determining whether or not all the CSV files 2 ₁ and 2 ₂ are associated with the processed status value (Y) (= processing is completed). If the result of this determination is that processing has not ended (= no), the process moves to step S2. When the processes for all the CSV files 2 ₁ and 2 ₂ are completed, the process proceeds to step S11 and the process is terminated. Here, there are two CSV files (user.csv, sosiki.csv) 2 ₁ , 2 ₂ , but since the processing has not been completed for the _two CSV files 2 ₁ , 2 ₂ , the process proceeds to step S 2.

(Step S <b> 2) The control unit 34 individually sends unconverted CSV files to the data conversion unit 35 among the CSV files 2 ₁ and 2 ₂ acquired by the input unit 33. Specifically, the control unit 34 refers to the CSV process management information in the CSV process management unit 32 and individually sends out the CSV file related to the unprocessed status value to the data conversion unit 35. For example, and it sends select the first CSV file (user.csv) _{2 1} to the data converting unit 35.

(Step S3) the data converter 35, compared CSV file (user.csv) _{2 1} transmitted from the control unit 34, by referring to the entry relationship definition 31d in the rule definition part 31, the file name of the CSV file It is determined whether or not the reference destination CSV name related to has a non-applicable value “−”. When it has a non-applicable value (when there is no reference destination), the process proceeds to step S4. In the case of not (if there is a reference destination), the data converter 35, compared CSV file (user.csv) _{2 1} transmitted from the control unit 34, CSV processing management information and the CSV process management section 32 with reference to entry relationship definition 31d rule definition unit 31, the CSV file (user.csv) _{2 1} filename (user) referenced CSV file name indicated by the reference destination CSV name associated with (sosiki) is It is determined whether or not it is associated with the processed status value (Y) in the CSV process management information.

  If the result of this determination is no, the process returns to step S2. If it is associated with the processed status value (Y), the process proceeds to step S4. Here, since the CSV file name (sosiki) of the reference destination is associated with the unprocessed status value “N” and corresponds to the case of NO, the process returns to step S2.

(Step S2) control unit 34, the second CSV file (Sosiki.Csv) sends Select _{2 2} to the data conversion unit 35.

In the next step S3 to S7, schematically, the data conversion unit 35, when the CSV file _{2 2} transmitted from the control unit 34 of the tissue CSV file _{2 2} has a hierarchical structure, the tissue CSV file 2 _2, based on a hierarchical structure defined 31e, into a first data _{4 1} LDIF format of arranging the organization name to the organization ID order based on level organization ID. Details will be described below.

See (Step S3) the data converter 35, compared CSV file (sosiki.csv) _{2 2} sent, which refers to an entry relationship definition 31d in the rule definition part 31, associated with the file name of the CSV file It is determined whether or not the destination CSV name has a non-applicable value “−”. As a result of the determination, since there is a non-applicable value “−”, the process proceeds to step S4.

(Step S4) the data converter 35, the CSV file (Sosiki.Csv) to _{2 2,} the values of the hierarchical structure defined 31e in the rule definition part 31 (ORG_ID, HIGH_ORG_ID) tissue ID field that matches (ORG_ID) And the higher organization ID item (HIGH_ORG_ID) is determined. As a result of the determination, a CSV file having the organization ID item and the upper organization ID item is selected as an organization CSV file having a hierarchical structure, and the process proceeds to step S5. Move. If the result of determination is no, the process moves to step S8. Here, since the hierarchy item and the upper hierarchy definition item of the target CSV file (sosiki.csv) are defined in the hierarchy configuration definition 31e, the process proceeds to step S5.

  (Step S5) The data conversion unit 35, in accordance with the definition contents of the hierarchy configuration definition 31e, the organization ID item (ORG_ID) that defines the hierarchy of the CSV file (sosiki.csv) to be converted, and the upper organization ID that defines the upper hierarchy Specify the item (HIGH_ORG_ID). Based on the identified organization ID item (ORG_ID) and higher organization ID item (HIGH_ORG_ID), the data conversion unit 35 rearranges the organization ID and the upper organization ID in descending order from the highest layer (the upper layer is NULL). The rearranged result is as shown in the second to third columns from the left in FIG. After the rearrangement is completed, the process proceeds to step S6.

  (Step S6) The data conversion unit 35 refers to the attribute mapping definition 31b and the arrangement configuration definition 31c on the basis of the rearranged organization ID and higher organization ID, and the organization ID in ascending order for each “ou” of the LDIF data. The directory item identification name dn (distinguished name) indicating the tree point is individually shown from each through the upper hierarchy ID to the highest hierarchy ID, and the process proceeds to step S7.

(Step S7) Based on the dn, the attribute mapping definition 31b and the object class mapping definition 31a created in Step S6, the data conversion unit 35, in the order of the organization ID based on the higher organization ID, as shown in FIG. (ou), organization name (orgName), creates a first data _{4 1} LDIF format arranged telephone number (telephoneNumber) and object class (objectClass). As the first data 4 ₁ form, for example, dn, leaving the organization ID and organization name, it may be modified so as to omit the other data (phone number). This kind of modification can be realized by appropriately defining the LDIF data of the attribute mapping definition 31b as "-".

After creating the first data _{4 1} LDIF format, the control unit 34, as shown in FIG. 11, the converted CSV file (sosiki.csv) _{2 2} unprocessed status values CSV processing management unit 32 in association with (N) is updated to the processed status value (Y), and the process returns to step S1.

(Step S1) The control unit 34 refers to the CSV process management information in the CSV process management unit 32, and determines whether or not the processes of all the CSV files 2 ₁ and 2 ₂ have been completed. Here, since although one CSV file (sosiki.csv) _{2 2} processing is terminated, the other CSV file (user.csv) _{2 2} of the processing is not finished, the flow proceeds to step S2.

(Step S2) the control unit 34 refers to the CSV process management information in the CSV processing management unit 32, and select the CSV file (user.csv) _{2 1} associated with the raw status value to the data conversion unit 35 Send to step S3.

Incidentally, the next step S3 to S4, S8～S9, in S7, schematically, the data conversion unit 35, when the CSV file _{2 1} transmitted from the control unit 34 is a user CSV file _{2 1} with reference relationship converts the user CSV file _{2 1,} based on the entries relationship definition 31d, the second data _{4 2} in LDIF format of arranging the username for each user ID. Details will be described below.

(Step S3) data conversion unit 35 to _{2 1} to the delivery CSV file (user.csv), with reference to the entry relationship definition 31d in the rule definition part 31, associated with the file name of the CSV file It is determined whether or not the reference CSV name has a non-applicable value “−”. Data conversion unit 35, a CSV file (user.csv) to _{2 1,} with reference to the entry relationship definition 31d of CSV processing management information and the rule definition part 31 of the CSV processing management unit 32, the CSV file (user .csv) 2 Whether or not the CSV file name (sosiki) of the reference destination indicated by the reference destination CSV name related to the file name (user) of ₁ is associated with the processed status value (Y) in the CSV process management information Determine. Here, it determines with being related with the processed status value (Y), and moves to step S4.

(Step S4) the data converter 35, the CSV file (user.csv) to _{2 1,} the values of the hierarchical structure defined 31e in the rule definition part 31 (ORG_ID, HIGH_ORG_ID) tissue ID field that matches (ORG_ID) And whether it has a higher organization ID item (HIGH_ORG_ID). Here, it determines with it being no and moves to step S8.

(Step S8) data converting unit 35 determines on the basis of whether the CSV file (user.csv) _{2 1} has a reference relationship to the entry relationship definition 31d. Specifically, the data conversion unit 35, for this CSV file (user.csv), belongs organization ID item (SYOZOKU) that matches the value (SYOZOKU) of the reference source item of the entry relation definition 31d in the rule definition unit 31 As a result of this determination, the CSV file having the belonging organization ID item is selected as a user CSV file having a reference relationship, and the process proceeds to step S9. If the result of determination is no, the process proceeds to step S10. Here, since the CSV file (user.csv) has the belonging organization ID item (SYOZOKU) that matches the value (SYOZOKU) of the reference source item of the entry relationship definition 31d, the process proceeds to step S9.

(Step S9) data conversion unit 35, among the first data 4 ₁ associated with the tree points of arrangement definition 31c, associated with tissue ID that matches the value of the reference source field of the entry relationship definition 31d "SYOZOKU" The directory item identification name dn is read out, and the user ID related to the organization ID and the dn are arranged to create a new dn related to the user ID. The created result is as shown in FIG. After creating the directory item identification name dn, the process proceeds to step S7.

(Step S7) Based on the dn, attribute mapping definition 31b, and object class mapping definition 31a created in step S9, the data conversion unit 35, for each dn and user ID (uid), as shown in FIG. (cn), mail (mail) and the second to create the data _{4 2} LDIF format arranged telephone number (telephoneNumber), the LDIF format second data _{4 2} writes to continue after the first data _{4 1} to create a third data _{4 3.} As the second data 4 ₂ forms, for example, dn, leaving the user ID and the user name, it may be modified so as to omit the other data (e-mail and phone number). This type of modification can be realized by appropriately defining the LDIF data of the attribute mapping definition 31b as "-".

After data creation, control unit 34 associates the converted CSV file (user.csv) _{2 1,} the processed status value raw status value of CSV processing management information in the CSV processing management unit 32 (N) ( Y) and return to step S1.

  (Step S1) The control unit 34 refers to the CSV process management unit 32, and determines whether or not the process has been completed for all the CSV files. Here, since the processing of the two CSV files (user.csv, sosiki.csv) has been completed, the process proceeds to step S11 and ends.

  Although not applicable in the above example, if there is no reference relationship in step S8, the data conversion unit 35 proceeds to step S10. In step S10, the data conversion unit 35 creates a directory item identification name dn based on the definition contents of the attribute mapping definition 31b and the arrangement configuration definition 31c, and proceeds to step S7.

  Next, it is assumed that steps S0 to S11 are completed in this way.

Control unit 34 sends the third data 4 ₃ created by the data converting unit 35 is completed to the output unit 36. The output unit 36 outputs the third data _{4 3} as one LDIF file 4 to LDAP directory device 20.

  In the LDAP directory device 20, when the LDIF input unit 22 receives the LDIF file 4, the LDIF input unit 22 imports the LDAP file 4 and converts it into the LDAP hierarchical structure data. As shown in FIG. Store in the data storage unit 21.

As described above, according to the present embodiment, the input unit 33 acquires the CSV files 2 ₁ and 2 ₂ from the relational database device 10, and the data conversion unit 35 receives the CSV files 2 ₁ and 2 sent from the control unit 34. of 2 _2, the tissue CSV file _{2 2} having the hierarchical structure, based on a hierarchical structure defined 31e, into a first data _{4 1} LDIF format of arranging the organization name to the organization ID order based on the upper organization ID, see the user CSV file _{2 1} having a relationship, on the basis of the entry relationship definition 31d, converted for each user ID in the second data _{4 2} LDIF format of arranging the user name, second data 4 after the first data _{4 1} create a third data _{4 3} LDIF format crowded ₂ calligraphy, the output unit 36 LDAP directory the third data _{4 3} as one LDIF file 4 And outputs it to the device 20.

As described above, when converting a plurality of CSV files 2 ₁ , 2 ₂ having a hierarchical structure or a reference relationship into LDIF format data 4 ₁ , 4 ₂ , 4 ₃ , the definitions written in the rule definition unit 31 in advance Since the conversion is performed based on 31a to 31e, the trouble of creating the conventional schema mapping definition files 3 ₁ and 3 ₂ can be eliminated, and the burden on the operator can be reduced.

  Supplementally, the LDAP directory data conversion apparatus 30 can easily generate the LDIF file 4 expressing the hierarchical structure and the entry relation as shown in FIG. 13 by defining the minimum information regarding the hierarchical structure and the reference relation. Since it can be created, the burden on the user can be reduced.

In contrast, conventionally, as shown in FIG. 14, CSV file _{2 1,} 2 2, ..., every _{2 n,} the schema mapping definition file _{3 1,} 3 2 ..., requires the need to create a _{3 n} This is burdening the user.

  Note that the method described in the above embodiment includes a magnetic disk (floppy (registered trademark) disk, hard disk, etc.), an optical disk (CD-ROM, DVD, etc.), a magneto-optical disk (MO) as programs that can be executed by a computer. ), And can be distributed in a storage medium such as a semiconductor memory.

  In addition, as long as the storage medium can store a program and can be read by a computer, the storage format may be any form.

  In addition, an OS (operating system) running on a computer based on an instruction of a program installed in the computer from a storage medium, MW (middleware) such as database management software, network software, and the like realize the above-described embodiment. A part of each process may be executed.

  Further, the storage medium in the present invention is not limited to a medium independent of a computer, but also includes a storage medium in which a program transmitted via a LAN, the Internet, or the like is downloaded and stored or temporarily stored.

  Further, the number of storage media is not limited to one, and the case where the processing in the above embodiment is executed from a plurality of media is also included in the storage media in the present invention, and the media configuration may be any configuration.

  The computer according to the present invention executes each process in the above-described embodiment based on a program stored in a storage medium, and is a single device such as a personal computer or a system in which a plurality of devices are connected to a network. Any configuration may be used.

  In addition, the computer in the present invention is not limited to a personal computer, but includes an arithmetic processing device, a microcomputer, and the like included in an information processing device, and is a generic term for devices and devices that can realize the functions of the present invention by a program. .

  Note that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. Moreover, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements over different embodiments may be appropriately combined.

  DESCRIPTION OF SYMBOLS 10 ... Relational database apparatus, 11 ... Table storage part, 11a ... User table definition, 11b ... Organization master table definition, 11c ... User master data, 11d ... Organization master data, 12 ... CSV output part, 20 ... LDAP directory apparatus, 21 ... Data storage unit, 22 ... LDIF input unit, 30 ... LDAP directory data conversion device, 31 ... Rule definition unit, 31a ... Object class mapping definition, 31b ... Attribute mapping definition, 31c ... Arrangement configuration definition, 31d ... Entry relationship definition, 31e ... hierarchical structure definition, 32 ... CSV process management unit, 33 ... input unit, 34 ... control unit, 35 ... data conversion unit, 36 ... output unit.

Claims (3)

For each set ID item having a set ID as a value, set information in a table format in which a set name item having a set name as a value and a higher set ID item having a higher set ID as a value and an element ID having an element ID as a value An element name item having an element name as a value for each item and element information in a table format in which an allocation set ID item having an allocation set ID as a value is associated; a set CSV file obtained by converting the set information into a CSV format; A relational database device capable of outputting each CSV file composed of element CSV files obtained by converting the element information into CSV format;
An LDAP directory device that receives the LDIF file and imports the LDIF file;
And an LDAP directory data conversion program used in an LDAP directory data conversion apparatus provided with storage means,
The LDAP directory data converter is
Means for writing, in the storage means, hierarchical configuration definition information in which a hierarchical item having a set ID item as a value and an upper hierarchical definition item having a higher set ID item as a value are associated with each file name of the aggregate CSV file;
For each file name of each CSV file, a reference destination CSV file name or a reference destination CSV name having a non-applicable value, a reference source allocation set ID item or a reference source item having a non-applicable value, and a reference destination set Means for writing reference relationship definition information associating ID items or reference destination items having non-applicable values to the storage means;
Obtaining means for obtaining each CSV file from the relational database device;
Of the obtained CSV files, unconverted file sending means for individually sending unconverted CSV files;
When the sent CSV file is a set CSV file having a hierarchical configuration, the set CSV file is an LDIF format first in which set names are arranged in the order of the set ID based on the upper set ID based on the hierarchical configuration definition information. First data conversion means for converting into one data;
When the sent CSV file is an element CSV file having a reference relationship, the element CSV file is converted into second data in LDIF format in which element names are arranged for each element ID based on the reference relationship definition information. Second data conversion means for
LDIF data creation means for creating the third data in the LDIF format by writing the second data so as to continue after the first data;
Creation completion data sending means for sending third data for which the creation has been completed;
Output means for outputting the transmitted third data to the LDAP directory device as one LDIF file;
LDAP directory data conversion program for functioning as The LDAP directory data conversion program according to claim 1,
The LDAP directory data converter is
Means for writing CSV processing management information associating each acquired CSV file with an unprocessed status value into the storage means;
Means for updating the unprocessed status value of the CSV process management information to a processed status value in association with the converted CSV file for each conversion of the first and second data converting means;
Further function as
The creation completion data sending means includes
Means for referring to the CSV processing management information in the storage means to determine whether all CSV files are associated with the processed status value;
If all the CSV files in the CSV process management information are associated with the processed status value as a result of the determination, means for sending third data to the output means;
Contains
The unconverted file sending means is means for individually sending a CSV file related to the unprocessed status value with reference to the CSV processing management information in the storage means when the result of the determination is negative. The first data conversion means includes
Whether the reference CSV name related to the file name of the CSV file has a non-applicable value with reference to the reference relation definition information in the storage means for the CSV file sent by the unconverted file sending means No reference destination determination means for determining whether or not
If the result of determination by the non-reference destination determination means is negative, the CSV process management information and reference relationship definition information in the storage means are referred to for the CSV file sent by the unconverted file sending means. Reference destination processed determination means for determining whether the CSV file name of the reference destination indicated by the reference destination CSV name related to the file name of the CSV file is associated with the processed status value in the CSV process management information When,
As a result of determination by the reference destination absence determination means, when the reference destination CSV name has a non-applicable value, or as a result of determination by the reference destination processing completion determination means, the CSV file name of the reference destination indicated by the reference destination CSV name is processed. When it is associated with the completed status value, it is determined whether or not the CSV file has a set ID item and a superset ID item that match each value of the hierarchical configuration definition information in the storage means. As a result, a set file selecting means for selecting a CSV file having a set ID item and a super set ID item as a set CSV file having the hierarchical structure;
Contains
The second data conversion means includes
As a result of the determination in the set file selection means, an assigned set ID item that matches the value of the reference source item of the reference relationship definition information in the storage means for a CSV file having no set ID item and no higher set ID item. Element file selection means for selecting whether or not the CSV file having the assigned set ID item as the element CSV file having the reference relationship as a result of the determination;
An LDAP directory data conversion program comprising: For each set ID item having a set ID as a value, set information in a table format in which a set name item having a set name as a value and a higher set ID item having a higher set ID as a value and an element ID having an element ID as a value An element name item having an element name as a value for each item and element information in a table format in which an allocation set ID item having an allocation set ID as a value is associated; a set CSV file obtained by converting the set information into a CSV format; A relational database device capable of outputting each CSV file composed of element CSV files obtained by converting the element information into CSV format;
An LDAP directory device that receives the LDIF file and imports the LDIF file;
LDAP directory data conversion devices that can communicate with each other,
Hierarchy definition storage means for storing, for each file name of the aggregate CSV file, hierarchy configuration definition information in which a hierarchy item having a set ID item as a value and an upper hierarchy definition item having an upper set ID item as a value are associated;
For each file name of each CSV file, a reference destination CSV file name or a reference destination CSV name having a non-applicable value, a reference source allocation set ID item or a reference source item having a non-applicable value, and a reference destination set A reference definition storage means for storing reference relationship definition information in association with an ID item or a reference destination item having a non-applicable value;
Obtaining means for obtaining each CSV file from the relational database device;
Of the obtained CSV files, unconverted file sending means for individually sending unconverted CSV files;
When the sent CSV file is a set CSV file having a hierarchical configuration, the set CSV file is an LDIF format first in which set names are arranged in the order of the set ID based on the upper set ID based on the hierarchical configuration definition information. First data conversion means for converting into one data;
When the sent CSV file is an element CSV file having a reference relationship, the element CSV file is converted into second data in LDIF format in which element names are arranged for each element ID based on the reference relationship definition information. Second data conversion means for
LDIF data creation means for creating the third data in LDIF format by writing the second data so as to continue after the first data;
Creation completion data sending means for sending the third data that has been created;
Output means for outputting the sent third data as one LDIF file to the LDAP directory device;
An LDAP directory data conversion apparatus comprising:

Images