JP4079990B2 - Generation method of object integrated management system - Google Patents

Description

  The present invention relates to a system for integrated management of different types of data existing in a distributed manner in a network environment such as a database or a server.

  It is normal for various types of databases to be introduced even in existing companies. There is usually no compatibility between these databases. In addition, it becomes necessary to add or delete a data management system that manages data of different formats such as databases and servers distributed in such a network environment.

  In Patent Document 1, “Regarding a method of equivalently handling objects without regard to the storage location of the objects, a logical object that represents the object in the logical layer and a connector object that implements access to the object are created, and both Describes a database integrated application construction system that manages the relationship using a conversion table. Here, when performing integrated management of objects, it is necessary to modify the connector object and conversion table that implements processing to access the object, and management of the configuration of the integrated management target is distributed. It was necessary to devise.

Japanese Patent Laid-Open No. 11-96054

  In order to uniformly access different data existing in a distributed manner, Patent Document 1 prepares a logical object and a connector object, and manages the correspondence between them using a conversion table. At this time, when adding new data as a management target as an integrated data management system, it is necessary to add a logical object and a connector object and to correct a conversion table. This method has a problem in that the system management and maintenance costs are low due to lack of flexibility in system expansion and modification.

  An object of the present invention is to make it possible for a metamodel management unit to centrally manage various distributed data structures and access processing management as an object integrated management system, and manage objects according to the metamodel. In other words, it is intended to realize efficient data integration management processing and reduction of maintenance cost necessary for system configuration management.

  In order to achieve the above object, a repository that stores a class definition called a metamodel part and an instance of the class called an object part as a persistent object according to an object orientation is used. The metamodel part of this repository stores a virtual object metamodel and an adapter object metamodel, and the object part stores a virtual object corresponding to actual data and an adapter object having a function of accessing the actual data from the virtual object. Has been. An object integrated management system is constructed by providing a metamodel management unit (creating, deleting, and changing metamodel information) and an object management unit (creating, deleting, and changing objects) that manage these. Further, the metamodel management unit models actual data and a data management system that manages the actual data and manages them as a metamodel. The object management unit manages objects as instances of the metamodel managed by the metamodel management unit. The metamodel management unit centrally manages the configuration of the data management system to be managed by the object integrated management system. The object management unit generates virtual object and adapter object instances from the metamodel. Management of these metamodel information is executed by using an interface provided by the object integrated management system.

  Here, modeling the data management system means that if the data management system is a relational database, for example, the database is represented by the database name, format, table configuration, column name, and the like. A meta model is definition information that defines a model.

  According to the present invention, in an object integrated management system that integrates and manages actual data held by various data management systems, the addition and deletion of the data management system can be facilitated, and the cost required for system management, construction, and maintenance can be reduced. I can do it.

  Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is an overall view including an embodiment of an object integrated management system of the present invention. The object integrated management unit (102) includes a metamodel management unit (104) and an object management unit (105), and stores information managed by each in the repository (106). Actual data to be integrated and managed are distributed in a network environment, and various data management systems exist depending on the type of the actual data. Data management system 1 (113) using a relational database, data management system 2 (114) using a document database for storing document data, etc., and those using other databases, databases There is a data management system 3 (115) for managing actual data and providing means for accessing the actual data.

  The object integrated management unit (102) implements integrated management for the actual data managed by these various forms of data management systems 1 to 3 (113, 114, 115). The object integrated management unit (102) is configured by the meta model management unit (104) and the object management unit (105) to configure the system and data for the data management systems 1 to 3 (113, 114, 115) and the actual data managed there. Manage information and execute access to actual data. The object management unit (105) manages the object (111, 112) as an instance of a class called a meta model (109, 110) defined by the meta model management unit (104). Further, the object management unit (105) manages the actual data held by the data management systems 1 to 3 (113, 114, 115), the configuration information such as the location and type of the data management systems 1 to 3, and the data The real data is accessed using the adapter object (112) having a function of access processing for the real data stored in the management system.

  By using the object access interface (103) provided by the object integrated management unit (102), the data user (101) uses a plurality of data management systems 1 to 1 without being aware of the actual data location and storage format. 3 (113, 114, 115) can be accessed uniformly. At this time, the object integrated management unit (102) provides an integrated management function expandability to the various data management systems 1 to 3 (113, 114, 115) by adding adapter objects.

  FIG. 2 shows a data format stored in the repository (106). Data stored in the repository (106) is classified into a metamodel part (107) and an object part (108). When the data management system A (201) holds data 1 (203) and data 2 (204) in the database (202), there is a class (205) called DATA as a metamodel (109) of the virtual object. It is defined that “name” is a string type as an attribute value. There is a data management system class (206) as a meta model (110) of the adapter object, and the attribute value "system name" is a string type, and implementation of processing to acquire and store actual data as its operation Define. This processing is processing using an access language provided by the database (202). In other words, the adapter object metamodel (110) has a definition of a method for manipulating data. In addition, a relationship is defined (207) between the DATA class and the data management system class.

  The object part stores the virtual object (111) and the adapter object (112) as instances of the class defined in the metamodel part. As virtual objects (111), there are data1 (208) and data2 (209) objects corresponding to data 1 (203) and data 2 (204) stored in database (202) which is actual data. Thus, there are as many virtual objects as the number of data.

  An object of system1 (210) exists as an adapter object (112). One adapter object exists for each data management system. Although the adapter object has been defined earlier, it has a function of retrieving or writing actual data based on the virtual object. Specifically, it has a method consisting of compiled program modules. Virtual objects and adapter objects are instances of their respective metamodels. When the instance is generated, the related information (211) is also set between the objects of data1 (208), data2 (209) and system1 (219) according to the related definition (207) defined in the meta model. . This related information (211) is set by holding a reference to an object with which each object is related internally (specifically, providing a pointer) according to object orientation.

  FIG. 3 shows a specific example of the data format stored in the repository (106) when the database (302) of the data management system B (301) is a relational database. The meta model (110) of the adapter object in the meta model part (107) is composed of RDB (304), TABLE (305), COLUMN (306) classes that model a relational database, and their related definitions (307, 308). .

  In the object part (108), the objects rdb1 (312), table1 (313), col 1 (314), col 2 (315), col 3 (316) and their related information (317, 318) are included as adapter objects (112). Exists. The related information is set by holding a reference to an object to which each object is related internally according to object orientation. The objects (312 to 316) constituting the adapter object (112) are created according to the configuration of the table existing in the database (302). The virtual object (111) is generated corresponding to the record existing in the table of the database (302). The column value of each record is stored as the attribute value of the virtual object (111).

  FIG. 4 shows the relationship between the metamodel in the repository (106) in the object integrated management system, the objects, and the actual data held by the data management system, and will be described together with the flowchart of FIG. The object integrated management system (102) receives the generation request of the adapter object (406) to the metamodel management unit (104) by the object access interface (103) (501).

  Upon receiving the request, the metamodel management unit (104) requests the repository (106) to generate the adapter object (406) (502), and the repository (106) generates an instance of the adapter object metamodel (402). Stored as an object (406) (503,504). The metamodel management unit (104) refers to the database (202) of the data management system A (201) using the adapter object (406), and acquires actual data (505). When real data exists (506), corresponding to the real data 1 (203) (408), the repository (106) generates a virtual object 1 (404) as an instance of the virtual object metamodel (401) (507,508). ). At this time, the virtual object 1 (404) sets an association (407) with the adapter object (406) according to the association (403) defined in the metamodel definition unit (509). This process is automatically performed by implementing it in the constructor called when creating an instance.

  The repository (106) stores the generated virtual object 1 (404) (510), and similarly generates the virtual object 2 (405) corresponding to the remaining real data 2 (204) (409). Store (511). The object management unit (105) manages the virtual objects stored in the repository (106) in such a relationship, so that the object integrated management system (102) can store the actual data held by various types of data management systems. Integrated management.

  Here, the case where the actual data (203, 204) is stored in the database (202) has been described, but the file stored in the storage device or the distributed data is not limited to the database as the actual data exists. Dynamic data on a memory that can be referred to by an object or a protocol can be a target of integrated management as a virtual object by implementing an access process for the actual data in the adapter object.

  FIG. 6 shows processing when a new data management system is added, and will be described with reference to the flowchart of FIG. Coordination with the data management system A (201) has already been defined, and in the repository (106) are the metamodel (604) of the virtual object A, the metamodel (606) of the adapter object A, and instances thereof. Virtual object 1 (612), virtual object 2 (613), and adapter object A (615) exist. At this time, a case where the data management system C (601) is newly linked will be described.

  First, when the data user (101) makes a request for adding the data management system C (601) to the object integrated management unit (102), the metamodel management unit (104) uses the object access interface (103) to make an adapter object C. A request to add the meta model (607) of the virtual object C and the meta model (605) of the virtual object C is received (701).

  Next, the metamodel management unit (104) executes processing for storing the requested metamodel (605,607) in the repository (106) (702), and the repository (106) stores the requested metamodel (605,607). (703).

  At this time, if the database (602) of the data management system C (601) is an access means similar to the database (202) of the data management system A (201), the meta model (607) of the adapter object C is converted to the adapter. It is defined that the object A has a meta model (606) and an inheritance relationship (608). In FIG. 6, the arrow of the relationship definition 608 indicates that the meta model of the adapter object C inherits the meta model of the adapter object A. As a result, the access processing implemented in the metamodel (606) of the adapter object A can be reused by the metamodel (607) of the adapter object C. In addition, when adding the same type of data management system, it is also possible to generate a plurality of instances from the metamodel (606) of the existing adapter object A to make the adapter object C (616). By defining a relationship (611) between the meta models of virtual objects, it becomes possible to handle the relationship of actual data between different data management systems. Specifically, defining a relationship between metamodels means that pointers to the objects of the other party have a one-to-many relationship.

  Next, as an instance of the metamodel definition added here, an adapter object C (616) and a virtual object 3 (614) are generated (704 to 714) as in FIG. At this time, the relationship (619) between the virtual objects is set in the instantiation process of the virtual object 3 (614) (712). These processes are requested by the object access interface (103) provided by the object integrated management unit (102), and the adapter object and the virtual object are stored in the repository (106) as instances of the respective metamodels in this way. The object integrated management unit (102) can newly add the data management system C (601).

  Similarly, the linked data management system can be deleted or modified. By using the object access interface (103), the object integrated management unit (102) provides a flexible and efficient configuration management function.

  FIG. 8 shows an example of a process in which a data user refers to an object using an object integrated management system, in which actual data is stored in a relational database, and will be described with reference to the flowchart of FIG. . The data user (101) can access various objects integrated and managed in a unified way using the object access interface (103) provided by the object integration management unit (102). . When the object access interface (103) receives the reference request for the virtual object A (309), it passes the request to the object management unit (105) (901).

  The object management unit (105) searches and acquires the virtual object A (309) using the function of the repository (106) (902, 903). The virtual object A (309) corresponds to a record (actual data) whose ID of the list table held in the database (802) of the data management system D (801) is 1. Therefore, in order to actually acquire the name and date value, the object management unit (105) acquires the adapter object D (112) associated with the virtual object A (309) (906) and uses it to perform the actual operation. Refer to the data value (907).

  At this time, in order for the adapter object D (112) to access the database (802) of the data management system D (801), the database name (910) from the rdb1 object (311) and the table name (911) from the table1 object (312) , Col 1 object (312), col 2 object (313), col 3 object (314) by getting column name (912) respectively, using the access language provided by database (802), data acquisition method (803) acquires the value of the actual data (913). The acquired value is returned to the data user (101) as a return value of the object access interface (103) (915, 917). At this time, the value of the actual data once acquired is stored as the attribute value of the virtual object (915). This makes it possible to improve the object reference access processing efficiency by returning the attribute value held by the virtual object as it is without accessing the actual data for the second and subsequent reference requests (916). It becomes. However, when the actual data held by the data management system is frequently updated, the value of the actual data is referred to every time.

  In some cases, the association of the adapter object is not set in the virtual object stored in the object part of the repository (106). This is a case where the repository (106) directly manages the object as real data, and in the case of such a virtual object, the object management unit (105) refers to the attribute value of the virtual object by the condition determination of (904). Returns its value.

  FIG. 10 shows a method of implementing a process for efficiently operating a target object by a data user (101) using related information in a virtual object as one application example of an object integrated management system. This will be described with reference to the flowchart of FIG. In the process of performing integrated object management, it may be necessary to trace the relationship between different objects and acquire a set of required objects. At this time, if the data user acquires the objects to be acquired one by one, the efficiency of the object reference processing is poor, and the amount of data flowing through the network between the data user and the object integrated management system increases. It takes time to acquire all the necessary objects.

  Therefore, in the object integrated management system of the present invention, it is possible to implement a method for executing user customization processing on a virtual object in the same manner as implementing a data acquisition method on an adapter object. For example, consider a process of acquiring the virtual object 2 (613) related to the virtual object 4 (1001). In the case where the object relations are simply acquired one by one, the virtual object 3 (614) related (1004) to the virtual object 4 (1001) is first acquired and further related to the virtual object 3 (614) (619) ) To obtain the virtual object 2 (613).

  At this time, useless processing of transferring the virtual object 3 (614) between the data user and the object integrated management system is performed. Therefore, the virtual object 2 acquisition method (1005) is implemented in the metamodel definition of the virtual object 4 (1001). When acquiring the virtual object 2 (613) related to the virtual object 4 (1001), first, the virtual object 2 acquisition method (1005) of the virtual object 4 (1001) is executed (1101, 1102). The virtual object 2 acquisition method (1005) acquires the virtual object 3 (614) related (1004) inside the object part (108) (1103), and further acquires the virtual object 2 (613) related (619). (1104). The virtual object 2 acquisition method (1105) returns the obtained virtual object 2 (613) to the data user (1105).

  This eliminates unnecessary data exchange between the data user and the object integrated management system, and it is efficient to execute complex object operations using multiple objects in the object part (108) and return only the results. It becomes possible to add a simple process. By implementing such user customization processing in the virtual object metamodel definition, it is possible to use it in all virtual objects that are instances thereof.

  FIG. 12 illustrates the layering of the object integrated management system in a large-scale system as one application example of the object integrated management system. The object integration management unit A (1201) treats the object integration management unit B (1202) and the object integration management unit C (1203) as one data management system. This can be done by preparing an adapter object that implements processing to refer to the object by the object access interface of the object integrated management system.

  When the two object integrated management units (1202, 1203) manage a plurality of data management systems (113 to 115), the data user (101) accesses the object integrated management unit A (1201). Real data held by all data management systems (1202, 1203, 113 to 115) can be accessed in a unified manner without being aware of the hierarchy. Such a mechanism is effective in constructing a distributed base system in a large-scale integrated operation management system that integrally manages various types of objects.

1 is an overall configuration diagram including an object integrated management system. It is a figure of the data format which an object integrated management system stores in a repository. FIG. 3 is a diagram of a data format when the management target system is a relational database as an example of FIG. 2. FIG. 5 is a relationship diagram between a metamodel definition managed by an object integrated management system and an object configuration. It is a flowchart figure of the process which comprises an object from the metamodel definition managed by the object integrated management system. It is a metamodel definition and the block diagram of an object at the time of adding the management object of an object integrated management system. It is a flowchart figure of the process at the time of adding the management object of an object integrated management system. It is a block diagram of an object when a data user refers to the object managed by the object integrated management system. It is a flowchart figure of a process when a data user refers to the object managed by the object integrated management system. It is a block diagram of the object at the time of mounting and mounting the user customization process in a virtual object. It is a flowchart figure of the user customization process in a virtual object. It is a block diagram when the object integrated management system is hierarchized.

Explanation of symbols

  101: Data user, client, 102, 1201, 1202, 1203: Object integration management unit, 103: Object access interface, 104: Meta model management unit, 105: Object management unit, 106: Repository, 107: Meta model unit, 108: Object part, 109, 401, 604, 605: Virtual object meta model, 110, 402, 606, 607: Adapter object meta model, 111, 404, 405, 612, 613, 614, 1001: Virtual object, 112, 406, 615, 616, 1002: Adapter object, 113-115, 201, 301, 601, 801, 1204-1206: Data management system, 202, 302, 602, 802, 603: 204 : Actual data

Claims (2)

In a system for integrated management of real data managed by a data management system, a virtual object created corresponding to each real data, a virtual object meta model defining a virtual object, configuration information of the data management system, and the A repository that stores an adapter object having a function of an access process to actual data stored in the data management system, an adapter object metamodel that defines the adapter object, the virtual object metamodel and the adapter object in the repository Oh comprising a metamodel management part that manages the meta model, and object management unit that accesses and manages the adapter object and the virtual object using the adapter object to real data A method of generating object integrated management system,
In response to the received adapter object generation request, the metamodel management unit makes an adapter object generation request to the repository, and the repository generates the adapter object that is an instance of the adapter object metamodel. Stored in the repository,
The metamodel management unit acquires actual data by referring to the database of the data management system using the generated adapter object, and the repository is an instance of the virtual object metamodel and is acquired. Generate the virtual object corresponding to the and store it in the repository;
The metamodel management unit and the repository execute generation and storage of the virtual object for each real data managed by the data management system . In a system that integrates and manages real data of a plurality of data management systems that manage real data, a first virtual object that defines a virtual object and a virtual object that are created corresponding to each real data for a data management system An object meta model, configuration information of the data management system, an adapter object having a function of an access process for actual data stored in the data management system, and a first adapter object meta model defining the adapter object are stored. A repository; a metamodel management unit that manages the first virtual object metamodel and the first adapter object metamodel in the repository; and the adapter object that manages the virtual object and the adapter object. A method of generating object integrated management system that includes a object management unit for access by utilizing transfected into real data,
In response to the request to add the second metamodel for the new data management system, the metamodel management unit recycles the access processing implemented in the first adapter object metamodel. Generating a second adapter object metamodel in which an inheritance relationship with the first adapter object metamodel is defined, and a second virtual object metamodel in which an association with the second adapter object metamodel is defined Stored in the repository
In response to the received generation request for the second adapter object, the metamodel management unit makes a generation request for the second adapter object to the repository, and the repository creates an instance of the second adapter object metamodel. Generating and storing the second adapter object in the repository;
The metamodel management unit acquires actual data by referring to the database of the new data management system using the generated second adapter object, and the repository is an instance of the second virtual object metamodel. A second virtual object corresponding to the acquired actual data is stored in the repository,
The method for generating an object integrated management system, wherein the metamodel management unit and the repository execute generation and storage of the second virtual object for each real data managed by the new data management system .

Images