JP6677809B2 - Adapter generation apparatus and method - Google Patents

Description

  The present invention relates to an adapter generation apparatus and method, for example, an adapter generation apparatus that generates an adapter that converts data of a data model such as a CIM (Common Information Model) into data of a relational database (RDB: Relational Data Base) format. It is suitable for application.

  In recent years, there has been a demand for collecting and accumulating various kinds of data and providing new added value by analyzing the accumulated data in an integrated manner, for example, as in big data analysis. Under such circumstances, if data formats are mixed, preparation work for data analysis takes time and the convenience is impaired. Therefore, international standardization (standardization) of a standard data model CIM (Common Information Model) is promoted. ing.

  As one of methods for handling data expressed in CIM (hereinafter referred to as CIM data), there is a method of managing the CIM data as data of a relational database. By accumulating the CIM data as data of the relational database, the CIM data can be easily accumulated by the function of the RDBMS (RDBMS), and the analysis of the CIM data can be easily realized by the function of the RDBMS. .

  However, in order to manage the CIM data in the relational database, an adapter for exchanging the CIM data with an external system (for example, a client computer) (hereinafter referred to as a CIM adapter) is required.

  The CIM adapter has a function of converting between a CIM object representation and a relational model of a relational database, and a conversion between CIM / XML (Extensible Markup Language) for exchanging CIM data. If the content or version of the CIM changes (that is, if the CIM profile changes), the CIM adapter must be prepared each time. For this reason, the development cost of the CIM adapter is very large.

  Patent Literature 1 discloses a data processing device and method capable of creating an instance including a plurality of versions of an ontology. According to the data processing apparatus and method disclosed in Patent Document 1, there is provided an apparatus and method for automatically generating a data sheet for inputting an instance of a predetermined class for CIM profiles having different versions, and the development cost is reduced. Can be reduced.

International Publication No. 2014/189056 JP 2010-249924 A

  However, in the technology disclosed in Patent Literature 1, one instance creation unit has only one data output unit. For example, when it is desired to obtain an output result obtained by combining a plurality of CIM profiles, the technology is disclosed in Patent Literature 1. There is a problem that cannot be dealt with by the technology.

  Patent Document 2 discloses an apparatus and a method for automatically generating a plurality of data access components for the purpose of supporting efficient system development. However, these apparatuses and methods do not support a set of a plurality of classes having a hierarchical structure such as a CIM data model.

  Also, by combining the inventions of Patent Document 1 and Patent Document 2, it may be possible to automatically generate a data access component having a plurality of data output formats corresponding to the CIM data model. Data access components are required for all combinations of upgrades, customer development, types of CIM profiles, the number of classes per CIM profile (maximum several hundred classes), and SQL patterns, and the number is enormous.

  The present invention has been made in view of the above points, and an object of the present invention is to propose an adapter generating apparatus and method capable of easily and quickly creating an adapter for converting a data format.

  In order to solve such a problem, in the present invention, a data format of data of a predetermined data model having a first data format is converted into a second data format according to a relational database, or the second data format is used. An adapter generation device that generates an adapter that converts the data of the first data format into the first data format, and a storage unit that stores one or a plurality of the adapters generated by the adapter generation unit Mapping, wherein the adapter generation unit associates a profile and a version of the data model, a table of the relational database, and a query to the relational database with respect to a subset for output for each data output format. Generate information and the adapter Holds management information including information on a tool and rules for data conversion used for data, information on a script for performing data conversion processing, and information on a format of a definition, and specifies, based on the mapping information and the management information, The adapter is generated in accordance with the specified data output format.

  Further, in the present invention, the data format of the data of the predetermined data model having the first data format is converted into a second data format corresponding to a relational database, or the data of the second data format is converted to the second data format. 1. An adapter generation method executed in an adapter generation device that generates an adapter that converts data into one data format, wherein the adapter generation device includes a data model profile and an output subset for each data output format. Versions, mapping information for associating tables in the relational database, queries to the relational database, respectively, information on tools and rules for data conversion used when generating the adapter, and scripts for performing data conversion processing Information and definition A first step of setting management information including information about a format, and the adapter generation device generates the adapter according to the specified data output format based on the mapping information and the management information. The second step is provided.

  ADVANTAGE OF THE INVENTION According to this invention, the information processing apparatus and method which can produce an adapter easily and in a short time can be implement | achieved.

FIG. 1 is a block diagram illustrating an example of an overall configuration of a system according to an embodiment. FIG. 3 is a conceptual diagram illustrating a configuration example of a CIM adapter common unit. It is a conceptual diagram which shows the example of a structure of a CIM adapter different part. FIG. 4 is a conceptual diagram illustrating a configuration example of mapping information. It is a conceptual diagram which shows the example of a structure of SP mapping information. It is a conceptual diagram which shows the example of a structure of PCT mapping information. It is a conceptual diagram which shows the example of a structure of T-SI mapping information. It is a conceptual diagram which shows the example of a structure of SI-SQL mapping information. FIG. 4 is a conceptual diagram illustrating a configuration example of management information. FIG. 4 is a conceptual diagram illustrating a configuration example of use tool information. It is a conceptual diagram which shows the example of a structure of Java (trademark) conversion rule information. FIG. 4 is a conceptual diagram illustrating a configuration example of O / R map definition information. It is a conceptual diagram which shows the example of a structure of acquisition function definition information. FIG. 4 is a schematic diagram schematically illustrating a configuration example of a mapping information / management information screen. It is a flowchart which shows the example of the operation | work procedure of CIM adapter difference part production | generation work. It is a flowchart which shows the processing procedure of CIM interface generation processing. It is a flowchart which shows the processing procedure of a code output process. It is a figure showing the example of RDF format data of a CIM profile. FIG. 6 is a diagram illustrating an example of an output profile. FIG. 4 is a diagram illustrating an example of XML schema data. FIG. 4 is a diagram illustrating an example of an RDB table creation SQL. FIG. 4 is a diagram illustrating an example of a Java class file. FIG. 10 is a diagram illustrating an example of a CIM / XML-compatible Java class file after Java conversion rules are applied. It is a figure showing an example of output of data acquisition SQL. It is a figure showing an example of an output of an O / R map definition. FIG. 14 is a diagram illustrating an output example of an acquisition function definition. It is a figure showing an example of an output of a servlet program.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In addition, this does not limit the present invention. Further, in the following description, processing may be described with “program” as a subject. However, a program executes a predetermined process by executing a processor (for example, a CPU) included in a computer, a storage device, or the like. The processing may be performed by using a processor as the subject of the processing because the processing is appropriately performed using a storage resource (for example, a memory) and / or a communication interface device (for example, a communication port).

  The processing described with the program as the subject may be processing performed by a processor or a device (a computer, a storage device, or the like) having the processor. Further, the processor may include a hardware circuit that performs part or all of the processing. The program may be installed in each controller from a program source. The program source may be, for example, a program distribution computer or a storage medium.

  In the following description, an identifier, a number, or a name is used as element identification information, but the identification information may include other types of information instead or in addition thereto.

(1) Configuration of Computer System According to the Present Embodiment In FIG. 1, reference numeral 1 denotes a computer system according to the present embodiment as a whole. In this computer system 1, one or a plurality of client computers 2 are connected to a server device 4 and a database server device 5 via a first communication network 3, and the database server device 5 is connected to a server device 1 via a second communication network 6. Alternatively, it is configured to be connected to a plurality of storage devices 7.

  The client computer 2 includes a CPU (Central Processing Unit) 11, an input / output unit 12, a storage unit 13, and an interface 14 connected via an internal bus 10.

  The CPU 11 is a processor that controls the operation of the entire client computer 2. The input / output unit 12 includes an output unit including a liquid crystal display for displaying various information and a GUI (Graphical User Interface), and an input unit including a keyboard and a mouse for the user to input instructions and information. And a part.

  The storage unit 13 includes a semiconductor memory and / or a hard disk drive (HDD: Hard Disk Drive), and is used to store various programs and data. When the CPU 11 executes the program stored in the storage unit 13, various processes of the entire client computer 2 are executed. The storage unit 13 may be directly connected to the CPU 11 without passing through the internal bus 10.

  The storage unit 13 stores an application 15 and a client program 16. The application 15 is a program having a function of executing various processes according to the work of the user using the client computer 2, and exchanges CIM data with the server device 4 via the client program 16 in the XML format.

  The interface 14 is a hardware device having a function of performing a protocol control when the client computer 2 communicates with the server device 4 or the like via the first communication network 3, and is configured by, for example, a NIC (Network Interface Card). You.

  The server device 4 generates a query (hereinafter, appropriately referred to as SQL (Structured Query Language)) according to the request from the client computer 2, transmits the generated query to the database server device 5, and is provided from the database server device 5. The execution result of the SQL is transmitted to the client computer 2, the CIM data provided from the client computer 2 is converted into a data format of a relational database and transmitted to the database server device 5, or the relational database acquired from the database server device 5 Is a computer having a function of converting the data of the above into a data format of CIM data and transmitting the data to the client computer 2.

  The server device 4 includes an interface 21, a CPU 22, an input / output unit 23, and a storage unit 24 connected via an internal bus 20. The interface 21, the CPU 22, the input / output unit 23, and the storage unit 24 have the same functions and configurations as the corresponding parts of the client computer 2 (the interface 14, the CPU 11, the input / output unit 12, or the storage unit 13). The detailed description here is omitted.

  The storage unit 24 of the server device 4 stores a CIM adapter common unit 25 described later, one or more CIM adapter different units 26, and a CIM adapter generation unit 27. The CIM adapter common unit 25 is a functional block embodied by the CPU 22 executing a program (not shown) stored in the storage unit 24, and includes various tools such as data conversion tools registered in advance, Java conversion rules, and the like. And various definition information such as O / R map definition information and acquisition function definition information.

  Like the CIM adapter common unit 25, the CIM adapter different unit 26 is a functional block embodied by the CPU 22 executing a program (not shown) stored in the storage unit 24, and includes one or more types of CIM profiles. Is a data conversion unit that generates CIM data corresponding to the data output format of the above and converts the CIM data of the corresponding data output format into the data format of the relational database or vice versa.

  The CIM adapter generation unit 27 is a functional block embodied by the CPU 22 executing a program (not shown) stored in the storage unit 24. The CIM adapter generation unit 27 holds mapping information 28 and management information 29 given in advance. Based on the information 28 and the management information 29, for example, by using a tool, rule, and definition information designated by a CIM adapter developer or the like from among various tools, rules, and definition information registered in the CIM adapter common unit 25, The CIM adapter difference unit 26 is generated according to the output subset specified as the data output format of the new CIM profile.

  The database server device 5 has a function of registering and managing the CIM data transmitted from the client computer 2 and converted into the data format of the relational database in the server device 4 in the relational database 42 stored in the storage device 7. It is.

  The database server device 5 includes a first interface 31, a CPU 32, an input / output unit 33, a storage unit 34, and a second interface 35 connected via an internal bus 30. The first interface 31, the CPU 32, the input / output unit 33, and the storage unit 34 have the same functions and configurations as the corresponding parts (the interface 14, the CPU 11, the input / output unit 12, or the storage unit 13) of the client computer 2. Therefore, detailed description here is omitted.

  The second interface 35 is a hardware device having a function of performing a protocol control when the database server device 5 communicates with the storage device 7 via the second communication network 6, and includes a NIC or the like.

  The storage unit 34 of the database server device 5 stores an RDBMS (Relational Data Base Management System) 36 that manages the relational database 42 stored in the storage device 7. The RDBMS 36 executes the SQL provided from the server device 4 and transmits the execution result to the server device 4.

  The storage device 7 is a large-capacity storage device, and includes a storage unit 40 formed of one or a plurality of storage devices, and a control unit 41 that controls input and output of data to and from the storage unit 40.

  As a storage device of the storage unit 40, for example, an expensive disk such as a SCSI (Small Computer System Interface) disk, an inexpensive disk such as a SATA (Serial AT Attachment) disk or an optical disk, or a semiconductor memory is used. In this case, a plurality of types of storage devices may be provided in the storage unit 40. The data of the above-described relational database 42 is stored in a storage area provided by the storage unit 40.

  The control unit 41 includes an information processing resource such as a CPU and a memory, and is connected to the communication network 6. The control unit 41 stores data provided from the RDBMS 36 in the relational database 42 or stores requested data from the relational database 42 in accordance with the SQL provided from the RDBMS 36 of the database server device 5 via the second communication network 6. The data is read and transferred to the RDBMS 36 via the second communication network 6.

  Note that a network such as a LAN (Local Area Network) or a WAN (Wide Area Network) can be applied as the first communication network 3, and the second communication network 6 is configured with a fiber channel or the like. Network (for example, SAN (Storage Area Network)) can be applied.

  FIG. 2 shows a configuration example of the CIM adapter common unit 25 held in the storage unit 24 of the server device 4. The CIM adapter common unit 25 includes a storage area 50 for storing and holding one or more registered XML schema conversion tools, a storage area 51 for storing and holding one or more registered relational database table creation tools, A storage area 52 for storing and holding one or more registered Java conversion tools, a storage area 53 for storing and holding one or more registered O / R map tools, and one or more registered Java conversion tools And a storage area 54 for storing the Java conversion script. However, instead of providing all of these storage areas 50 to 54 from the beginning, the corresponding storage areas 50 to 54 may be added when the corresponding tool is registered.

  FIG. 2 shows “EA Tool” as an XML schema conversion tool, “EA Tool” as an RDB table creation tool, “JAXB” and “Original Tool” as Java conversion tools, “MyBatis” as an O / R map tool, and Java. An example is shown in which “Script1” and “Script2” are registered as conversion scripts.

  FIG. 3 shows a configuration example of the CIM adapter different part 26. As is clear from FIG. 3, the CIM adapter different part 26 includes an output profile 60, an XML schema data file 61, a relational database table creation SQL file 62, a Java class file 63, and a CIM / XML compatible Java class file 64. , A data acquisition SQL file 65, an O / R map definition file 66, an acquisition function definition file 67, and a servlet program 68.

  The output profile 60 is a tool to be used when generating one or a plurality of data output formats (output subsets) corresponding to one or a plurality of CMI profiles and a CIM adapter different part 26 corresponding to the data output format. Is a profile that defines the combination of the CIM adapter and the CIM adapter. As will be described later with reference to FIG. 19, in the output profile 60, among the combinations of a plurality of tools set in the use tool information 80 (FIG. 10) described later with reference to FIG. A combination of tools to be used when generating the unit 26 and a subset ID set in SP mapping information 70 (FIG. 5) described later with reference to FIG. 5 are specified.

  The XML schema data file 61 is a file in which XML schema data as shown in FIG. 20, for example, obtained by converting a corresponding CIM profile using an XML schema conversion tool is stored.

  The relational database table creation SQL file 62 includes, for example, an SQL (relational database table creation SQL) as shown in FIG. 21 for creating a relational database table corresponding to a Java class constituting the CIM profile in the relational database. The stored file.

  The Java class file 63 is a file in which data obtained by converting XML schema data into a Java class, for example, as shown in FIG. 22, is stored. The CIM / XML compatible Java class file 64 stores the Java class in a CIM / XML compatible Java. This is a file that stores, for example, data as shown in FIG. 23 converted into a class.

  Further, the data acquisition SQL file 65 is a file in which, for example, SQL (data acquisition SQL) as shown in FIG. 24 for acquiring data from the corresponding relational database table is stored, and the O / R map definition file 66 is For example, as shown in FIG. 25, the CIM adapter difference unit 26 stores an O / R map definition that is mapping information that associates Java class objects with corresponding tables in a relational database. Further, the acquisition function definition file 67 is a file in which an acquisition function as shown in FIG. 26, for example, which is a function for acquiring necessary data from the relational database table, is stored. For example, a program as shown in FIG.

  Among these files, the XML schema data file 61, the relational database table creation SQL file 62, and the Java class file 63 store the CIM adapter difference unit 26 and the relational database table corresponding to the CIM adapter difference unit 26 in the relational database. Used when generating.

  The data acquisition SQL file 65, the O / R map definition file 66, and the acquisition function definition file 67 are completed when necessary codes are stored at the stage when the CIM adapter different part 26 is generated, and are actually given from the client computer 2. In response to the read request or the write request, the client computer 2 stores the CIM data provided in the XML format in the corresponding relational database table, or converts the data read from the relational database table into the XML format and converts the data into the XML format. It is used for data format conversion when transmitting to the computer 2.

  In practice, a read request or a write request specifying one of the servlet programs 68 is given to the server device 4 from the client computer 2. Then, for example, when the write request and the write target CIM data are given from the client computer 2, the server device 4 changes the data format of the CIM data from the XML format to the relational format using the CIM / XML-compatible Java class file 64. The data is converted into a data format corresponding to the database, and the converted data is stored in the corresponding relational database table using the O / R map definition file 66 and the acquisition function definition file 67.

  When the read request is given from the client computer 2, the server device 4 uses the data acquisition SQL file 65, the O / R map definition file 66, and the acquisition function definition file 67 to store the corresponding data in the relational database. The data is read from the corresponding table, the data format is converted from the data format corresponding to the relational database to the XML format data using the CIM / XML compatible Java class file 64, and this is transmitted to the client computer 2.

  FIG. 4 shows a specific configuration of the mapping information 28 held by the CIM adapter generation unit 27 stored in the storage unit 24 of the server device 4. As shown in FIG. 4, the mapping information 28 is obtained from SP mapping information 70, PCT mapping information 71, T-SI mapping information 72, and SI-SQL mapping information 73, which are defined in advance by the user. Be composed.

  The SP mapping information 70 is information indicating the correspondence between the output subset, the profile name of the CIM profile, and the version thereof. As shown in FIG. 5, the output subset ID column 70A, the profile name column 70B and a table structure having a version column 70C.

  An identifier (subset ID) assigned to each output subset is stored in the output subset ID column 70A, and a CIM corresponding to the output subset is stored in the profile name column 70B and the version column 70C. The profile name (profile name) and its version are stored.

  Therefore, in the case of the example in FIG. 5, the subset for output having the subset ID “Sub1” is a CIM profile with the profile name “Profile1” having the version “1.0” and a profile with the profile name “Profile2” having the version “1.0”. The CIM profile of FIG.

  The PCT mapping information 71 is information indicating the correspondence between the CIM profile and its version, the class of Java, and the table in the relational database 42 (FIG. 1). As shown in FIG. It has a table structure including a column 71A, a version column 71B, a Java class name column 71C, and a relational database table name column 71D.

  In the profile name column 71A and the version column 71B, the profile name of each CIM profile and its version name are stored, respectively. In the Java class name column 71C, each profile name and version associated with the CIM profile of the profile are stored. The class names of Java classes are stored. The relational database table name field 71D stores the table name of the table on the relational database 42 that is associated with the corresponding Java class on a one-to-one basis.

  Therefore, in the case of the example of FIG. 6, the CIM profile of the version “1.0” with the profile name “Profaile1” is associated with the four Java classes “AAAA”, “BBBB”, “CCCC” and “DDDD”. For example, among them, it is shown that the Java class “AAAA” is associated with the table with the table name “T_AAAA” on the relational database 42.

  The T-SI mapping information 72 is information indicating the correspondence between each table on the relational database 42 stored in the storage device 7 and the SQL for referring to the table, and as shown in FIG. It has a table structure including a table name column 72A and a SQL ID column 72B.

  The relational database table name column 72A stores the table names of the respective tables of the relational database 42 stored in the storage device 7, and the SQL ID column 72B stores the identifiers (SQL) of each SQL that can be used for the corresponding table. SQL ID) are stored.

  Therefore, in the case of the example of FIG. 7, for example, a table having a table name of “T_AAAA” or a table having a table name of “T_BBBB” on the relational database 42 is provided with an SQL ID of “1” or “2”. The type of SQL can be used, and for a table with a table name of “T_CCCC”, in addition to the two types of SQL statements, it is also possible to use an SQL provided with an SQL ID of “3”. Have been.

  Further, the SI-SQL mapping information 73 is information indicating a correspondence between the SQL ID and the SQL, and has a table structure including an SQL ID column 73A and an SQL column 73B as shown in FIG. The SQL_ID column 73A stores an identifier (SQL ID) assigned to each SQL, and the SQL column 73B stores the specific content of the SQL to which the corresponding SQL ID is assigned.

  Therefore, in the case of the example of FIG. 8, for example, the content of the SQL provided with the SQL ID “1” is “Select * Rrom [T];” (all information of the table [T] is acquired). It is shown.

  On the other hand, as shown in FIG. 9, the management information 29 includes use tool information 80, Java conversion rule information 81, O / R map definition information 82, and acquisition function definition information 83.

  Among them, the Java conversion rule information 81 is information on rules when the CIM adapter generation unit 27 converts the CIM profile data converted into XML schema data into a Java class using a Java conversion tool, as described later. As shown in FIG. 11, it has a table structure including a Java conversion rule ID column 81A, a Java conversion rule content column 81B, and a script path name column 81C.

  In the Java conversion rule ID column 81A, an identifier (Java conversion rule ID) assigned to each Java conversion rule created by the user in advance is stored. Here, the Java conversion rule refers to a rule for converting CIM data from the client computer 2 into Java program code by a Java conversion tool or vice versa.

  The Java conversion rule content column 81B stores the specific content of the corresponding Java conversion rule, and the script path name column 81C stores the script obtained by scripting the processing of the corresponding Java conversion rule content. The absolute path name to is stored.

  The O / R map definition information 82 is information on the O / R map definition output by the CIM adapter generation unit 27. As shown in FIG. 12, the O / R map definition ID column 82A and the O / R map definition A content column 82B is provided.

  The O / R map definition ID column 82A stores an identifier (O / R map definition ID) assigned to each O / R map definition created in advance by the user, and stores the O / R map definition contents. The column 82B stores the specific contents of the corresponding O / R map definition.

  Therefore, in the case of the example of FIG. 12, it is indicated that the definition of the O / R map to which the O / R map definition ID of “1” is assigned has the contents as shown in FIG. Note that, in the O / R map definition content column 82B shown in FIG. 12, a portion surrounded by a broken line DL1 is a portion that is additionally output for each relational database table by the CIM adapter generation unit 27.

  The acquisition function definition information 83 is information on the definition of the acquisition function output by the CIM adapter generation unit 27. As shown in FIG. 13, the acquisition function definition information 83 has a table structure including an acquisition function definition ID column 83A and an acquisition function definition content column 83B. Have.

  The acquisition function definition ID column 83A stores an identifier (acquisition function definition ID) assigned to each acquisition function created in advance by the user, and the acquisition function definition content column 83B stores the corresponding acquisition function. Is stored.

  Therefore, in the case of the example of FIG. 13, it is shown that the definition of the acquisition function to which the acquisition function definition ID “1” is given has the content as shown in FIG. In the acquisition function definition content column 83B shown in FIG. 13, the portions enclosed by broken lines DL2 to DL4 are portions that are additionally output by the CIM adapter generation unit 27 for each relational database table.

  The use tool information 80 includes a Java conversion tool, a Java conversion rule, an O / R map tool, an O / R map tool, which are used when the CIM adapter generation unit 27 generates the CIM adapter different units 26 corresponding to various output profiles. This is information defining a combination of an R map definition and an acquisition function definition. As shown in FIG. 10, a use tool ID column 80A, a Java conversion tool column 80B, a Java conversion rule ID column 80C, and an O / R map tool column 80D , An O / R map definition ID column 80E and an acquisition function definition ID column 80F.

  An identifier (use tool ID) assigned to each combination of tools to be used is stored in the use tool ID column 80A, and a plurality of Java conversion tools prepared in advance are stored in the Java conversion tool column 80B. Among (a tool for converting CIM data into Java program code and performing the reverse conversion), the name of a Java conversion tool to be used in a combination of corresponding tools and the like (hereinafter, referred to as a tool combination) is stored. You.

  In the Java conversion rule ID column 80C, the identifier (Java conversion rule ID) of the Java conversion rule to be used in the tool combination among the various Java conversion rules included in the Java conversion rule information 81 as described above is stored. You.

  The O / R map tool column 80D stores the name of an O / R map tool to be used in a corresponding tool combination among a plurality of O / R (Object / Relational) map tools prepared in advance. Here, the O / R map tool is a tool that associates each data of a Java object with each item constituting a record of a relational database, so that the record of the relational database can be intuitively treated as an object.

  Further, in the O / R map definition ID column 80E, among the various O / R map definitions included in the O / R map definition information 82 as described above, the identifier of the O / R map definition to be used in the tool combination ( O / R map definition ID) is stored in the acquisition function definition ID column 80F, as described above, of the acquisition function definition identifier (acquisition function definition ID) to be used in the tool combination in the acquisition function definition information 83. Is stored.

  FIG. 14 shows a mapping information / management information setting screen 90 that can be displayed on an output unit such as a liquid crystal display constituting the input / output unit 23 when a user performs a predetermined operation on the input / output unit 23 of the server device 4. Using this mapping information / management information setting screen 90, the user can set the above-described mapping information 28 and management information 29 to a desired state.

  On the mapping information / management information setting screen 90, the SP mapping information 70, the PCT mapping information 71, the T-SI mapping information 72, and the SI that constitute the mapping information 28 described above with reference to FIGS. -Associating the SQL mapping information 73 with the use tool information 80, the Java conversion rule information 81, the O / R map definition information 82, and the acquisition function definition information 83 which constitute the management information 29 described above with reference to FIGS. Tabs 91A to 91H are provided.

  Each of the tabs 91A to 91H has information corresponding to the tab 91A to 91H (SP mapping information 70, PCT mapping information 71, T-SI mapping information 72, SI-SQL mapping information 73, A setting area 92 for setting use tool information 80, Java conversion rule information 81, O / R map definition information 82, or acquisition function definition information 83) is provided. In the setting area 92, FIG. A table 93 having the same form as the corresponding table shown in FIGS. 10 to 13 is displayed. In this case, the user can input desired setting values in each column of the table 93, and thus the user can set the mapping information 28 and the management information 29 to desired contents. I have.

  On the lower right side of the mapping information / management information setting screen 90, a save button 94 and a cancel button 95 are displayed. Then, on the mapping information / management information setting screen 90, the user sets the mapping information 28 and the management information 29 to desired contents using the tabs 91A to 91H, and then clicks a save button 94 to set the mapping set at that time. The setting values of the information 28 and the management information 29 can be saved. By clicking the cancel button 95, the setting values of the mapping information 28 and the management information 29 set using the tabs 91A to 91H can be saved. It can be canceled without any change.

  In this embodiment, the mapping information / management information setting screen 90 is used for setting the mapping information 28 and the management information 29. For example, the setting values of each information are written in a setting file, and A file may be read to set each information.

(2) Creation of CIM Adapter Difference Unit (2-1) Work of CIM Adapter Developer FIG. 15 shows an operation procedure when creating the CIM adapter difference unit 26. This operation is assumed to be performed by the CIM adapter developer, but may be performed by another person such as a system administrator. Note that the requirement definition and design of the CIM profile have been defined, and it is assumed that, for example, RDF format data of the CIM profile as shown in FIG. 18 has already been created.

  When generating the CIM adapter difference unit 26, the CIM adapter developer first stores a directory for storing the files 60 to 67 and the servlet program 68 described above with reference to FIG. 3 in the storage unit 24 of the server device 4 (FIG. 1). (S1).

  Subsequently, the CIM adapter developer creates a new output profile 60 (FIG. 3) corresponding to the new CIM profile, and stores the created output profile 60 in the directory created in step S1 (S2).

  FIG. 19 shows a configuration example of the output profile 60. In this example, one row corresponds to one output subset, and a plurality of output subsets can be specified by defining a plurality of rows. In one line, the usage tool ID set in the usage tool information 80 (FIG. 10) described later is specified after “ToolID =”, and the SP mapping information 70 (FIG. 5) described later after “SubsetID =” ) Is specified. For example, in FIG. 19, “ToolID = 1, SubsetID = Sub1” means “Performs Java conversion with Java conversion rule ID“ 1 ”using“ JAXB ”as a Java conversion tool, and as an O / R map tool. Using "MyBatis", output the code of the O / R map definition information according to the O / R map definition content with the O / R map definition ID of "1", and the acquisition function definition with the acquisition function definition ID of "1" The process of “outputting the code of the acquisition function definition information according to the content” ”means“ performing “Profile1” and “Profile2” whose subset IDs correspond to “Sub1” ”.

  Next, the CIM adapter developer uses the XML schema tool stored in the storage area 50 (FIG. 2) corresponding to the XML schema tool of the CIM adapter common unit 25 to design the designed CIM as shown in FIG. The PDF data of the profile is converted into XML schema data (FIG. 20), and the XML schema data is stored in the directory created in step S1 as an XML schema data file 61 (FIG. 3) (S3).

  If a plurality of XML schema tools are stored in the storage area 50 of the CIM adapter common unit 25, one XML schema tool is selected from the XML schema tools and the process of step S3 is performed. If the XML schema tool is not stored in step S3, step S3 is manually performed.

  Thereafter, the CIM adapter developer uses the relational database table creation tool stored in the storage area 51 (FIG. 2) corresponding to the relational database table creation tool of the CIM adapter common unit 25 to create the designed CIM profile. By performing customization, an SQL for creating a relational database table (see FIG. 21) is created, and the created SQL is stored as a relational database table creating SQL file 62 (FIG. 3) in the directory created in step S1 (S4). .

  If a plurality of relational database table creation tools are stored in the storage area 51 of the CIM adapter common unit 25, one relational database table creation tool is selected from the tools and the process of step S4 is performed. If the relational database table creation tool is not stored in the storage area 51, this step S4 is performed manually. Note that the customization of the CIM profile is, for example, release of the reference constraint in the designed CIM profile.

  Subsequently, the CIM adapter developer uses the Java conversion tool stored in the storage area 52 (FIG. 2) corresponding to the Java conversion tool of the CIM adapter common unit 25 to obtain the XML schema data file obtained in step S3. The data 61 is converted into Java class data (see FIG. 22), and this data is stored in the directory created in step S1 as a Java class file 63 (FIG. 3) (S5).

  At this time, if a plurality of Java conversion tools are stored in the storage area 52 of the CIM adapter common unit 25, one of them is selected and the process of step S5 is performed, and the Java area is stored in the storage area 52. If no conversion tool is stored, step S5 is performed manually. By the process of step S5, a plurality of Java class files are created according to the XML schema data.

  Next, the CIM adapter developer sends the relational database table creation SQL (FIG. 21) created in step S4 to the RDBMS 36 (FIG. 1) of the database server device 5. The RDBMS 36 that has received the relational database table creation SQL executes the relational database table creation SQL to create the specified table (S6). Although the relational database table creation SQL shown in FIG. 21 describes only the SQL for table creation, an SQL for creating an index may be added as needed.

  Thereafter, the CIM adapter developer sets SP mapping information 70, PCT mapping information 71, T-SI mapping information 72, and SI-SQL mapping information 73 (S7), and uses tool information. 80, Java conversion rule information 81, O / R map definition information 82, and acquisition function definition information 83 are set (S8). The setting of such information may be performed using the mapping information / management information setting screen 90 described above with reference to FIG. 14, or may be performed by reading a setting file in which the setting values of each information are described. If the information that has been set is used, there is no need to set it again.

  Subsequently, the CIM adapter developer operates the server device 4 to cause the server device 4 to execute a CIM interface generation process described later with reference to FIG. 16 (S9). In performing the CIM interface generation processing, the directory created in step S1 is specified. Thereby, the CIM adapter different part 26 based on this directory is generated by the CIM interface generation processing.

  Then, the CIM adapter developer creates the servlet program 68 (FIG. 3) of the CIM adapter different part 26 created at this time, and stores the created servlet program 68 in the directory created in step S2 (S10). As described above, the CIM adapter different part generation operation is completed.

  In step S10, it is assumed that the template of the servlet program 68 is output to a file by the CIM adapter generation unit 27 and stored in the directory created in step S2, and that the CIM adapter developer fills in necessary places in the file. Is also good. Further, the servlet program 68 may be copied from another CIM adapter different part 26 and a necessary portion may be corrected.

(2-2) CIM Interface Generation Process FIG. 16 shows the CIM adapter of the server device 4 in which the generation of the CIM adapter difference unit 26 is instructed by the CIM adapter developer in step S9 of the adapter difference unit generation work described above with reference to FIG. 5 shows a processing procedure of CIM interface generation processing executed by the generation unit 27. When instructed by the CIM adapter developer to generate a CIM adapter difference unit 26, the CIM adapter generation unit 27 generates a corresponding CIM adapter difference unit 26 according to the processing procedure shown in FIG.

  Actually, when the CIM adapter generating unit 27 is instructed to generate the CIM adapter different unit 26, it starts this CIM interface generating process, and is first set by the CIM adapter developer in steps S7 and S8 in FIG. The data acquisition SQL file 65 (FIG. 3), the O / R map definition file 66 (FIG. 3), and the acquisition function definition file 67 (FIG. 3) are created based on the mapping information 28 and the management information 29, respectively. Are opened in the directory created in step S2 of FIG. 15 (S20).

  Subsequently, the CIM adapter generation unit 27 reads one unprocessed line of the output profile 60 stored in the directory in step S2 of FIG. 15, and reads the tool specified as “ToolID” and “SubsetID”. The ID and the subset ID are specified (S21). For example, in the case of the output profile 60 illustrated in FIG. 19, for the first row, “1” is specified as the tool ID and “Sub1” is specified as the subset ID.

  Next, the CIM adapter generation unit 27 refers to the SP mapping information 70 (FIG. 5) and specifies a profile and a version corresponding to the subset ID specified in step S21 (S22). For example, in the case of the example of the first line in FIG. 19, since the subset ID specified in step S21 is “Sub1”, if the SP mapping information 70 has the contents in FIG. Thus, “Profile1” with version “1.0” and “Profile2” with version “1.0” are specified.

  Further, the CIM adapter generation unit 27 specifies the Java class and the relational database table corresponding to the profile and version specified in step S22 with reference to the PCT mapping information 71 (FIG. 6) (S23). For example, if the profile and version specified in step S22 are “Profile1” and “1.0”, respectively, as described above, and the PCT mapping information 71 has the content shown in FIG. 6, in step SP23, “AAAA”, “BBBB”, “CCCC” and “DDDD” are specified as Java classes, and “T_AAAA”, “T_BBBB”, “T_CCCC” and “T_DDDD” are specified as relational database tables.

  Subsequently, the CIM adapter generation unit 27 executes the data acquisition SQL file 65 (FIG. 3), the O / R map definition file 66 (FIG. 3), and the acquisition function definition for the set of the Java class and the relational database table specified in step S23. A code output process described later with reference to FIG. 17 is executed by adding a code to each of the files 67 (FIG. 3) (S24).

  Thereafter, the CIM adapter generation unit 27 determines whether or not the code output process has been executed for all the relational database tables specified in step S23 (S25). When the CIM adapter generating unit 27 obtains a negative result in this determination, the process returns to step S24, and repeats the code output process for each unprocessed relational database table among the relational database tables identified in step S23.

  As a result, for example, the combination of the Java class and the relational database table specified in step SP23 is “AAAA” + “T_AAAA”, “BBBB” + “T_BBBB”, “CCCC” + “T_CCCC” and “DDDD” + “T_DDDD” In this case, the code output process 1000 is executed four times in total for each set of Java classes and relational database tables.

  Then, when the CIM adapter generation unit 27 obtains a positive result in step S25 by finishing executing the code output process for all the relational database tables specified in step S23, all the profiles and versions specified in step S22 are obtained. Then, it is determined whether or not the processing of steps S23 to S25 has been completed (S26).

  If a negative result is obtained in this determination, the CIM adapter generating unit 27 returns to step S23, and thereafter repeats the processing of steps S23 to SP26 until a positive result is obtained in step S26.

  Then, when the CIM adapter generation unit 27 obtains a positive result in step S26 by eventually executing the processing in steps S23 to S25 for all the profiles and versions specified in step S22, the CIM adapter generation unit 27 reads all the profiles and versions identified in step S22. It is determined whether or not the processes of steps S22 to S26 have been completed for the subset of (S27).

  If a negative result is obtained in this determination, the CIM adapter generating unit 27 returns to step S22, and thereafter repeats the processing of steps S22 to S27 until a positive result is obtained in step S27.

  Then, the CIM adapter generating unit 27 eventually obtains an affirmative result in step S27 by completing the processing in steps S23 to S26 for all the subsets read from the output profile 60 (FIG. 3) in step S22. Then, the data acquisition SQL file 65 (FIG. 3), the O / R map definition file 66 (FIG. 3), and the acquisition function definition file 67 (FIG. 3) are closed (S28), and then the CIM interface generation processing ends. .

  FIG. 17 shows the specific processing contents of the code output processing executed by the CIM adapter generation unit 27 in step S24 of the CIM interface generation processing.

  When the process proceeds to step S24 of the CIM interface generation process (FIG. 16), the CIM adapter generation unit 27 starts the code output process shown in FIG. 17, and first refers to the use tool information 80 (FIG. 10) and Based on the tool ID specified in step S21 of the interface generation process, a tool combination to be used for code output of the subset is specified (S30).

  For example, in the example of FIG. 10, when the tool ID specified in step S21 is “1”, “JAXB” is a Java conversion tool, and a Java conversion rule whose Java conversion rule ID is “1” is a Java conversion rule. "MyBatis" as an O / R map tool, an O / R map definition with an O / R map definition ID of "1" as an O / R map definition, and an acquisition function definition with an acquisition function definition ID of "1" as an acquisition function definition Each will be specified.

  Subsequently, the CIM adapter generation unit 27 refers to the Java conversion rule information 81 (FIG. 11) and, among the tool combinations specified in step S30, the Java conversion rule contents corresponding to the Java conversion rule ID and the script path name Is specified (S31).

  For example, in FIG. 11, when the Java conversion rule ID specified in step S30 is “1”, “the XML schema file is searched, the Roott class is specified, and“ @XmiElement ”of the class is changed to“ XmiAttribute ”. , "Search XML schema files to identify classes that have references to other CIM classes, replace class variables in referenced classes with Java-only classes, change setter / getter" and "XML schema A file is searched to identify a class having a reference to another CIM class, and a reference-only class is added to a reference destination class. " Scr / Script1 "," / Scr / Script2 "or" / Scr / Script2 ".

  Next, the CIM adapter generation unit 27 executes the script of the Java conversion rule content specified in step S31 on the data of the Java class file 63 (FIG. 3), thereby executing the CIM / XML-compatible Java class file 64 (FIG. 3). ) Is created, and the created CIM / XML-compatible Java class file 64 is stored in the directory created in step S1 of FIG. 15 (S32).

  For example, in FIG. 11, when the Java conversion rule ID specified in step S30 is “1”, the script “/ Scr / Script1” and the script “/ Scr / Script2” are executed, and the corresponding Java class is executed. A CIM / XML compatible Java class file 64 is created. FIG. 23 shows an example of a CIM / XML-compatible Java class file after executing “/ Scr / Script1”. In this example, a Root class to be converted is specified by the script (an example of a Java class in FIG. 22), and the Java class is represented by a portion surrounded by a broken line DL10 in FIG. Conversion processing is being performed.

  Subsequently, the CIM adapter generation unit 27 refers to the T-SI mapping information 72 (FIG. 7) and the SI-SQL mapping information 73 (FIG. 8) and specifies the CIM interface generation processing (FIG. 16) in step S23. The SQL for the relational database is specified, and the code of the specified SQL is added to the data acquisition SQL file 65 (FIG. 3) stored in the directory created in step S2 of FIG. 15 (S33).

  For example, in the example of FIGS. 7 and 8, when the relational database table is “T_AAAA”, the SQL output as the code of the data acquisition SQL is “Select * From [T];” whose SQL ID is “1”. , The SQL of “Select * From [T] Where nwmid = xxx;” with the SQL ID “2” is specified. In addition, when a code is added to the data acquisition SQL file 65, the relational database table name (in this case, “T_AAAA”) is inserted and written in the place of “[T]” in each SQL. In the output example of the data acquisition SQL code shown in FIG. 24, a portion surrounded by a broken line DL11 is an example of a code output to a relational database “T_AAAA”.

  Next, the CIM adapter generation unit 27 refers to the O / R map definition information 82 (FIG. 12) to identify the O / R map definition contents corresponding to the O / R map definition ID of the tool combination identified in step 30. (S34).

  Further, based on the Java class and relational database table specified in step S23 of FIG. 16 and the SQL ID and SQL specified in step S33, the CIM adapter generation unit 27 performs the O / R map definition specified in step S34. Then, the code is added to the O / R map definition file 66 (FIG. 3) set in step S8 of FIG. 15 (S35).

  For example, in the example of FIG. 12, when the O / R map definition ID is “1”, a portion surrounded by a broken line DL1 in the O / R map definition content column 82B is added to the O / R map definition file 66. . The other portions in the O / R map definition content column 82B are described when the O / R map definition file 66 is created. In the O / R map definition output example shown in FIG. 25, the portions surrounded by the broken line DL12 correspond to “AAAA” for the Java class, “T_AAAA” for the relational database table, and “1” and “2” for the SQL ID. This is an example of the output code.

  Thereafter, the CIM adapter generation unit 27 determines whether or not the processing of steps S33 to S35 has been executed for all the SQLs specified in the relational database table specified in step S23 of FIG. 16 (S36). ).

  When the CIM adapter generating unit 27 obtains a negative result in this determination, the process returns to step SP33, and thereafter, repeats the processing of steps S33 to S36 until obtaining a positive result in step S36.

  Then, when the CIM adapter generation unit 27 obtains an affirmative result in step S36 by completing execution of the processing in steps S33 to S35 for all SQLs specified in the relational database table specified in step S23, the acquisition is completed. With reference to the function definition information 83 (FIG. 13), the acquisition function definition content corresponding to the acquisition function definition ID is identified from the tool combinations identified in step S30 (S37).

  Subsequently, the CIM adapter generating unit 27 obtains the acquisition function definition file 67 (FIG. 3) set in step S8 in FIG. 15 based on the Java class specified in step S23 and according to the acquisition function definition content specified in step S37. Is added to the code (S38).

  For example, in the example of FIG. 13, when the acquisition function definition is “1”, each part surrounded by broken lines DL2 to DL4 in the acquisition function definition content column 83B is added to the acquisition function definition file 67. The other parts of the acquisition function definition are described when the acquisition function definition file 67 is created. In the output example of the acquisition function definition illustrated in FIG. 26, a portion surrounded by broken lines DL13 to DL15 is an example of a code output for the Java class “AAAA” and the Java instance name “aAAA”. Note that the Java instance name may be an arbitrary character string, and in this example, the first character of the Java class is a name with a lowercase letter.

  Then, the CIM adapter generation unit 27 thereafter ends the code output processing 1000 and returns to the CIM interface generation processing of FIG.

(3) Effects of the present embodiment In the computer system 1 having the above configuration, the CIM adapter generation unit 27 of the server device 4 executes the data acquisition SQL file 65 and the O / R map definition file of the CIM adapter difference unit 26. 66, since the code of the acquisition function definition file 67 is automatically generated, it is possible to reduce the number of CIM adapter development steps of the CIM adapter developer. Thus, according to the computer system 1 of the present embodiment, a CIM adapter can be created easily and in a short time.

  Further, according to the computer system 1, a plurality of output subsets can be specified in the output profile 60, and a plurality of profiles can be specified for each output subset. Various CIM profiles can be supported.

  Further, according to the computer system 1, since only the required SQL codes can be output based on the relational database table and the SQL mapping information, the effect that the size of the CIM adapter different part 26 can be suppressed can be obtained. be able to.

(4) Other Embodiments Although the present embodiment has been described above, the present invention is not limited to this embodiment, and can be variously modified without departing from the gist thereof.

  For example, in the above embodiment, the CIM adapter generation unit 27 automatically generates the codes of the data acquisition SQL file 65, the O / R map definition file 66, and the acquisition function definition file 67 in the CIM adapter different unit 26. Then, the CIM adapter difference unit 26 is created. As described above, the CIM adapter difference unit 26 has a one-to-one correspondence with a CIM profile, and a plurality of CIM adapter difference units 26 correspond to a plurality of CIM profiles. Is created. Other than this procedure, a means for specifying an existing CIM profile closest to the internal structure of the CIM profile to be created, copying the corresponding CIM adapter different part 26, and correcting the code only at the difference may be used. Further, even when there is no CIM profile to be created, the CIM adapter different part 26 may be created by designating only the output profile.

  In the above-described embodiment, the case where the data model is CIM has been described. However, the present invention is not limited to this, and the present invention can be widely applied to data models other than CIM.

  Further, in the above-described embodiment, a case is described in which a mapping information / management information setting screen 90 having a screen configuration as shown in FIG. 14 is applied as an interface for setting mapping information and management information, respectively. However, the present invention is not limited to this, and various other configurations can be widely applied as the configuration of the interface.

  DESCRIPTION OF SYMBOLS 1 ... Computer system, 2 ... Client computer, 4 ... Server device, 5 ... Database server device, 7 ... Storage device, 22, 32 ... CPU, 24, 34 ... Storage part, 25 ... CIM Adapter common part, 26 CIM adapter difference part, 27 CIM adapter generation part, 28 Mapping information, 29 Management information, 36 RDBMS, 42 Relational database, 60 Output file, 61 ... XML schema data file, 62 ... SQL file for creating relational database, 63 ... Java class file, 64 ... CIM / XML compatible Java class file, 65 ... Data acquisition SQL file, 66 ... O / R Map definition file, 67 ... Acquisition function definition file, 68 ... Servlet Program 70 ... SP mapping information 71 ... PCT mapping information 72 ... T-SI mapping information 73 ... SI-SQL mapping information 80 ... Used tool information 81 ... Java conversion rule information, 82... O / R map definition information, 83... Acquisition function definition information, 90... Mapping information / management information setting screen.

Claims (8)

The data format of the data of the predetermined data model having the first data format is converted into a second data format corresponding to a relational database, or the data of the second data format is converted into the first data format In an adapter generation device that generates an adapter to perform
An adapter generation unit that generates the adapter;
A storage unit for storing one or more adapters generated by the adapter generation unit,
The adapter generation unit,
For a subset for output for each data output format, a profile and version of the data model, a table of the relational database, and mapping information respectively associating a query to the relational database,
Management information including information on tools and rules for data conversion used when generating the adapter, information on a script for performing data conversion processing, and information on a definition format,
An adapter generation device that generates the adapter according to the specified data output format based on the mapping information and the management information. The adapter generation unit,
The adapter generation device according to claim 1, wherein the adapter is generated according to a plurality of the specified data output formats. The adapter generation device according to claim 1, further comprising an interface for setting each of the mapping information and the management information. The data model is
CIM (Common Information Model) defined by international standards,
The adapter is
The CIM data transmitted from the host device in the XML (Extensible Markup Language) format is converted into a data format corresponding to the relational database, or the CIM data managed in the relational database is converted into the XML format. The adapter generation device according to claim 1, wherein the adapter generation device converts the data into data. The data format of the data of the predetermined data model having the first data format is converted into a second data format corresponding to a relational database, or the data of the second data format is converted into the first data format An adapter generation method executed in an adapter generation device that generates an adapter to perform,
The adapter generation device associates the adapter generation device with a profile and version of the data model, a table of the relational database, and a query for the relational database for an output subset for each data output format. a first step of setting the mapping information to give,
Said adapter generating device, based on said mapping information and the management information, and a second step of generating the adapter in accordance with the designated data output format,
The management information includes information on tools and rules of data conversion used when generating the adapter, information on a script for performing data conversion processing, and information on a definition format.
An adapter generation method, characterized in that: In the second step, the adapter generation device includes:
The adapter generation method according to claim 5, wherein the adapter is generated according to a plurality of the specified data output formats. The adapter generation device,
An interface for setting the mapping information and the management information,
In the first step,
Adapter generation method according to claim 5, wherein the mapping information via the interface is set. The data model is
CIM (Common Information Model) defined by international standards,
The adapter is
The CIM data transmitted from the host device in the XML (Extensible Markup Language) format is converted into a data format corresponding to the relational database, or the CIM data managed in the relational database is converted into the XML format. The adapter generation method according to claim 5, wherein the adapter is converted into data.

Images