CN100485687C - Method and device for set-up disconnection data programmed model and its application - Google Patents

Abstract

The invention discloses a method and device for establishing a connectionless data programming model. The method includes: dividing service data objects into domain objects and data objects, and defining data objects according to domain objects; establishing a domain object model, and The domain object model generates a corresponding physical table model; establishes a corresponding relationship between the data object and the physical table; generates a data object-physical table mapping model according to the corresponding relationship. The invention also discloses a data access service method and system. The invention can reduce the workload of business development, improve the development efficiency, realize the decoupling of the business system and the physical table model, and improve the expansibility of the system.

Description

Method, device and application for establishing connectionless data programming model

technical field

The invention relates to data access technology, in particular to a method, device and application for establishing a connectionless data programming model.

Background technique

Currently, almost all information processing systems target specific types of data sources. In the information processing system, the access technologies for specific types of data sources mainly include: relational database access technology through JDBC (Java Database Programming Standard), or XML file access technology through XPath (XML path language).

With the extension of enterprise business, the enterprise information system is constantly expanding, or develop new functions on the original system, or integrate the original independent subsystems to realize enterprise information sharing. This means that enterprise information systems are always faced with the challenge of dealing with heterogeneous data sources. The so-called heterogeneous data sources refer to different data sources with significant differences in data organization structure and data reading and writing methods. For example, relational databases and XML file databases are obviously different in terms of data organization structure and data reading and writing methods. Heterogeneous data sources include: relational databases, object databases, XML (Extensible Modeling Language) files, WebService (Web services), and external information systems that can provide data information.

To this end, a set of data programming interfaces that have nothing to do with the data source type is defined to realize the decoupling between the information processing system and the data source (that is, to remove the dependency between the two, so that when one of them can be easily replaced, the other remains the same. Can work normally), is the need for the development of enterprise information systems. SDO (Service Data Objects, Service Data Objects) is a set of application programming interfaces that have been standardized at present. This set of interface specifications provides data users with standard and consistent data access methods and shields data storage between heterogeneous data sources. Take the difference. Through these interface specifications, easy decoupling between data providers and data users is achieved; the information processing system will access data through the standard SDO API (standard programming interface for service data objects), and the data provider will also use the standard SDO API provides data externally.

In order to enable data users to disconnect from the data provider during the process of using data, and only get in touch with the data provider when they start to read and write data at the end, it is necessary to establish a connectionless data programming model. The existing SDO modeling technology is only EMF (Eclipse Modeling Framework, Eclipse Modeling Framework) developed by Eclipse (an open source organization). The EMF modeling technical solution mainly has the following key processes:

1. Use Rational Rose (a software modeling tool) to create a set of class diagrams (XML can also be used to represent class diagrams), and generate .mdl files:

As shown in Figure 1, this group of class diagrams contains three classes: library (Library), author (Writer), book (Book). Among them, each class includes: class name, attribute (name), method. The lines between various types represent the calling relationship between them: it can be a containment relationship, such as between the library and the author, between the library and the book; it can also be an association relationship, such as between the author and the book.

2. Import the mdl into EMF, and EMF will automatically generate the SDO model in the following format:

platform: /resource/EMFModel/model/library.ecore

library

Book

tilte: EString

pages: EInt

Category: BookCategory

author: Writer

Library

 name: EString

writes: Writer

books: Book

Writer

 name: EString

books: Book

BookCategory

Mystery=0

ScienceFiction=1

Biography＝2

EMF does not layer the SDO model when modeling, but combines models of different levels without separating different object models, which increases the difficulty of developing and maintaining SDO data objects, and the development work large. Due to the failure to subdivide the models at different levels and define the corresponding metadata for each level of the model, the SDO model has poor scalability and maintainability, and it is difficult to integrate into a platform with strong versatility and introspection function.

Contents of the invention

One aspect of the present invention provides a method and device for establishing a connectionless data programming model, so as to reduce the workload of business development and improve development efficiency.

Another aspect of the present invention provides a data access service method and system to realize the decoupling between the business system and the physical table model and improve the scalability of the system.

For this reason, the technical scheme provided by the invention is as follows:

Embodiments of the present invention provide a method for establishing a connectionless data programming model, comprising the following steps:

Divide service data objects into domain objects and data objects, and define data objects according to domain objects;

Establishing a domain object model, and generating a corresponding physical table model from the domain object model;

establishing a corresponding relationship between the data object and the physical table;

A data object-physical table mapping model is generated according to the corresponding relationship.

An embodiment of the present invention is a device for establishing a connectionless data programming model, including:

A hierarchical unit for dividing service data objects into domain objects and data objects, and defining data objects according to domain objects;

The model building unit is used to respectively build data programming models of different layers, and the model building unit includes:

The domain object model establishment subunit is used to establish the domain object model;

A physical table model generating subunit, configured to generate a corresponding physical table model according to the domain object model;

The data object-physical table mapping model generating subunit is configured to generate a data object-physical table mapping model according to the corresponding relationship between the data object and the physical table.

A data access service method in an embodiment of the present invention, comprising:

Establish a group of connectionless data programming models including different levels, the data programming models include: domain object model, data object model, physical table model, data object-physical table mapping model;

Deploying the data programming model to the service/business layer of the system;

When the user accesses the data, the data from the heterogeneous data source is presented to the user through the data programming model.

A data access service system in an embodiment of the present invention includes: a service/business layer subsystem that provides services to users, an application integration layer subsystem, and an enterprise information layer subsystem. The enterprise information layer subsystem includes one or more For heterogeneous data sources, a data programming model device is deployed in the service/business layer subsystem, and a data intermediary service device is deployed in the application integration layer subsystem, and the data programming model device is used to provide a set of Different levels of connectionless data programming models, the different levels of connectionless data programming models include: domain object model, data object model, physical table model, data object-physical table mapping model; when users access data, by The data intermediary service device obtains data from heterogeneous data sources, and assembles these data into data objects conforming to the data programming model specification, and the data programming model device invokes the assembled data objects, and converts the data Objects are presented to the user.

From the technical solutions provided by the above embodiments of the present invention, it can be seen that the method of the present invention divides models of different levels through the abstraction and analysis of the models, and defines a complete structured structure that is independent of the implementation technology and separate from each other. The layered model enables developers to create SDO data objects and conduct business development without learning specific SDO implementation technologies, thereby reducing the workload of business development and improving development efficiency.

In addition, the present invention separates the domain model from the physical table model, and builds a layer of data object model on the domain model, so that system designers can design systems on the domain model, and business developers can create data on the domain model. Data objects are defined on the database, so as to realize the decoupling between the business system and the physical table model, and improve the scalability of the system.

Description of drawings

Fig. 1 is a schematic diagram of a group of class diagrams established with Rational Rose in the prior art;

Fig. 2 is the implementation flowchart of a preferred embodiment of the method for setting up the connectionless data programming model of the present invention;

3 is a schematic diagram of the relationship between data objects and domain objects in an embodiment of the method for establishing a connectionless data programming model in the present invention;

4 is a schematic diagram of the relationship between different hierarchical models in the embodiment of the method for establishing a connectionless data programming model in the present invention;

Fig. 5 is a functional block diagram of the first embodiment of the device for establishing a connectionless data programming model in the present invention;

6 is a functional block diagram of the second embodiment of the device for establishing a connectionless data programming model in the present invention;

Fig. 7 is an implementation flowchart of a preferred embodiment of the data access service method of the present invention;

Fig. 8 is a schematic diagram of the J2EE layered architecture and the location of the SDO of the present invention;

Fig. 9 is a functional block diagram of a preferred embodiment of the data access system of the present invention.

Detailed ways

In order to enable those skilled in the art to better understand the solution of the present invention, the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments.

The present invention carries out structural layering to SDO, respectively establishes service data object models of different levels: domain object model, data object model, physical table model, data object-physical table mapping model, and makes the models of these different levels separate from each other . In this way, during business development, data objects can be generated from basic domain objects according to business needs, thereby reducing the workload of business development and improving development efficiency.

With reference to the flow process of a preferred embodiment of the method for setting up the connectionless data programming model of the present invention shown in Fig. 2, this embodiment comprises the following steps:

Step 201: Hierarchize service data objects, which can be specifically divided into domain objects and data objects. And define data objects in terms of domain objects.

When defining a data object, all or part of one or more domain objects can be combined to form a data object according to the needs of business applications.

For example, in the domain object view shown in FIG. 3 , there are four domain objects, which are domain object 1, domain object 2, domain object 3, and domain object 4. Wherein, domain object 2 is associated with the other three domain objects respectively. According to business needs, domain object 1 and domain object 2 are combined as a data object.

Of course, other layering methods can also be used, as long as the metadata can be fully utilized, the development workload can be reduced and the development efficiency can be improved.

Step 202: Establish a domain object model, and generate a corresponding physical table model from the domain object model.

Identify the domain objects and their interrelationships required by the business. Among the four domain objects shown in FIG. 3 , domain object 2 includes domain object 1 , domain object 3 and domain object 4 respectively, and there is no association between domain object 1 , domain object 3 and domain object 4 .

IDE (Integrated Development Environment) modeling tools can be used to establish a domain object model that satisfies the relationship between objects. For example, use Rational Rose or PowerDesigner (a software modeling tool) to create a domain object model.

Step 203: Establish a correspondence between data objects and physical tables.

Since Rose's object model mainly supports three programming languages: Java, VC and VB, Naming-SQL (named SQL) can be introduced into SDO, and the corresponding relationship between data objects and physical tables can be established through Naming-SQL. The Naming-SQL refers to extracting the SQL statement originally embedded in the program code, putting it into another file specially storing the SQL statement, and replacing it with a unique identifier at the original SQL statement. In this way, the database administrator can centrally manage all SQL statements stored in a file, and can easily modify the tables queried in the SQL statement, query order, or query conditions without changing the query results of the SQL statement. In order to achieve the goal of optimal performance.

Of course, other programming languages can also be used to establish the correspondence between data objects and physical tables.

Step 204: Generate a data object-physical table mapping model according to the corresponding relationship between the data object and the physical table.

For example, the relationship between the different hierarchical models established in the embodiment of the present invention is shown in Figure 4:

The data object includes part of domain object 1, domain object 2, and domain object 3. Physical table model 1 corresponds to data object model 1, physical table model 2 corresponds to data object model 2, and physical table model 3 corresponds to data object model 3. The corresponding relationship between data objects and physical tables is established by naming SQL, and a data object-physical table mapping model is generated. It can be seen from Figure 4 that the data object model, domain object model, data object-physical table mapping model, and physical table model are separated from each other.

It can be seen that the method for establishing a connectionless data programming model in the present invention divides models of different levels through the abstraction and analysis of the models, and defines a complete structured hierarchical model that is independent of the implementation technology and separate from each other. It enables developers to establish SDO data objects and carry out business development without learning specific SDO implementation technologies. Through the structural subdivision of the domain model, data object model, physical table model, and data object-physical table mapping model, and defining the corresponding metadata for each model, the clear layering of the entire SDO modeling technology and based on Interface definition for model processing. Since complete metadata is provided, models at various levels can be introspectively integrated into different platforms and frameworks.

Based on the idea of layering service data objects, the invention also provides a device for establishing a connectionless data programming model.

Referring to Fig. 5, Fig. 5 shows the functional block diagram of the first embodiment of the device for establishing a connectionless data programming model in the present invention:

In this embodiment, it includes: a layering unit 51 and a model building unit 52 . Among them, the layering unit 51 is used to layer the service data objects, divide the service data objects into domain objects and data objects, and define data objects according to the domain objects; the model building unit 52 is used to , establish the data programming model of each layer respectively.

The model building unit 52 includes: a domain object model building subunit 521 , a physical table model generating subunit 522 , and a data object-physical table mapping model generating subunit 523 . in,

The domain object model building subunit 521 is used to build a domain object model according to the domain objects and their logical relationships determined by the hierarchical unit, and can use IDE (Integrated Development Environment) modeling tools to build a domain object model satisfying the relationship between objects. For example, use Rational Rose or PowerDesigner (a software modeling tool) to create a domain object model. The physical table model generation subunit 522 is used to generate a corresponding physical table model according to the domain object model, that is, convert the domain object model into a physical table model. The data object-physical table mapping model generation subunit 523 is configured to generate a data object-physical table mapping model according to the correspondence between data objects and physical tables.

Referring to FIG. 6, FIG. 6 shows a functional block diagram of the second embodiment of the device for establishing a connectionless data programming model in the present invention:

The difference from the embodiment shown in FIG. 5 is that in this embodiment, a correspondence relationship establishment subunit 524 is added to the model establishment unit, which is used to establish the data objects required to generate the data object-physical table mapping model by naming SQL. The corresponding relationship with the physical table. Naming-SQL (named SQL) is introduced into SDO, and the corresponding relationship between data objects and physical tables is established through Naming-SQL.

The process of establishing the corresponding relationship between data objects and physical tables through Naming-SQL includes:

1. Write a query SQL statement (give the statement a unique identifier, called "named SQL"): it finds all the fields corresponding to the attributes of the data object from the database table;

2. Specify the one-to-one correspondence between the attributes of the data object and the fields queried by "Query SQL", rather than the direct correspondence between the attributes of the data object and the fields of the physical table.

That is to say, by configuring the one-to-one correspondence between the attributes of the data object and the fields queried by the named SQL, an indirect correspondence between the data object and the physical table is established.

In this way, the data object-physical table mapping model generating subunit 523 can directly generate a data object-physical table mapping model according to the corresponding relationship, without having to independently determine the corresponding relationship between the data object and the physical table. Of course, a variety of subunits that support the establishment of correspondences in different languages can also be provided, which can be selected and used according to the application environment during system development.

The method and device for establishing a connectionless data programming model in the present invention can be applied in the J2EE (Java2 Enterprise Edition) architecture, enabling system designers to design systems on the domain model and business developers to define data objects on the domain model , realize the decoupling between the business system and the physical table model, and improve the scalability of the system.

Referring to the process flow of a preferred embodiment of the data access service method of the present invention shown in Figure 7, it includes the following steps:

Step 701: Establish a set of data programming models including different levels.

Different levels of data programming models include: domain object model, data object model, physical table model, data object-physical table mapping model. The establishment process of these different levels of data programming models has been described in detail above, and will not be repeated here.

Step 702: Deploy the data programming model to the service/business layer of the system.

Step 703: When the user accesses the data, present the data from the heterogeneous data source to the user through the data programming model.

Step 704: After the user modifies the data, update the data modified by the user to the heterogeneous data source through the data programming model.

Refer to the schematic diagram of the J2EE layered architecture and the location of the SDO shown in Figure 8:

Among them, 81 is the enterprise information layer, which is used to provide various information sources, such as DB (relational database), LEGACY (historical files), ERP (enterprise resource planning table), Message (message) and other information sources with different formats ; 82 is the application integration layer, through DMS (Data Mediator Service, data intermediary service) provides unified exit/entrance for the data of different information sources; 83 is the service/business layer, used for business processing of data, such as adopting EJB Enterprise JavaBean, a model), Bean, Service and other technologies provided for the development of server-side enterprise application components; 85 is the server-side display layer, which is used to arrange the processed data into a specific format, such as through JSP (JavaServer Pages, a A dynamic web page technology), Servlet (Java server applet), UI Management (user interface management) and other technologies; 86 is the client display layer, which is used to display data in a specific format to customers through pages or other visual windows, such as, It is provided to customers through Browser (web browser), PDA (handheld computer), Webservice (page server), etc.

As can be seen from this figure, the realization of the technical solution of the present invention belongs to the DMS (Data Mediator Service, data intermediary service) level, and the DMS receives data from heterogeneous data sources (such as relational database DB, XML file, message Message, etc.), such as, Through JDBC (Java Database Programming Standard), JCA (J2EE Connector Architecture), JAR-RPC (Java API for XML-based RPC, JAVA programming interface for accessing WebServices based on XML remote call), JMS (Java Message Service) These protocols obtain corresponding data from different data sources, and then pack these data into data objects conforming to the data programming model specification, and deliver them to the data programming model in the service/business layer of the system; The data programming model described above invokes the assembled data object and presents the data object to the user. For example, the attributes of data objects and the hierarchical relationship between these attributes can be displayed through a form on a web page.

Referring to Fig. 9, Fig. 9 is a functional block diagram of a preferred embodiment of the data access service system of the present invention:

In this embodiment, it includes: a service/business layer subsystem 91 , an application integration layer subsystem 92 and an enterprise information layer subsystem 93 . Among them, the service/business layer subsystem 91 is used to provide services for users; the application integration layer subsystem 92 is used to provide unified access/entry for data from different information sources; the enterprise information layer subsystem 93 is used to provide information data for the system , including one or more heterogeneous data sources, such as relational database DB, XML file, Message, etc.

A data programming model device 901 is deployed in the service/business layer subsystem 91 , and a data intermediary service device 902 is deployed in the application integration layer subsystem 92 . Among them, the data programming model device 901 is used to provide a set of connectionless data programming models including different levels, that is, to model the business data required by the business layer, including the organizational structure and source of the business data. When a user accesses data, the data intermediary service device 902 obtains data from heterogeneous data sources, and assembles these data into data objects conforming to the data programming model specifications, and the data programming model device 901 invokes the assembled data objects, and Data objects are presented to the user. After the user modifies the data, the data programming model device 901 updates the data modified by the user into the heterogeneous data source.

While the invention has been described by way of example, those skilled in the art will appreciate that there are many variations and changes to the invention without departing from the spirit of the invention, and it is intended that the appended claims cover such variations and changes without departing from the spirit of the invention.

Claims (11)

1. A method of building a connectionless data programming model, comprising the steps of:

dividing the service data object into a domain object and a data object, and defining the data object according to the domain object;

establishing a domain object model, and generating a corresponding physical table model by the domain object model;

establishing a corresponding relation between the data object and the physical table;

and generating a data object-physical table mapping model according to the corresponding relation.

2. The method of claim 1, wherein the step of defining the data object from the domain object in the domain object model comprises: all or part of one or more domain objects are combined to form a data object.

3. The method of claim 1, wherein the establishing a domain object model comprises:

determining domain objects required by the service and the mutual relation thereof;

and establishing a domain object model meeting the relation by utilizing an Integrated Development Environment (IDE) modeling tool.

4. The method of claim 1, wherein establishing the correspondence between the data object and the physical table comprises:

and establishing a corresponding relation between the data object and the physical table through naming SQL.

5. An apparatus for creating a connectionless data programming model, comprising:

the hierarchical unit is used for dividing the service data object into a domain object and a data object and defining the data object according to the domain object;

a model establishing unit for respectively establishing data programming models of different layers,

the model building unit includes:

a domain object model establishing subunit, configured to establish a domain object model;

the physical table model generating subunit is used for generating a corresponding physical table model according to the domain object model;

and the data object-physical table mapping model generating subunit is used for generating a data object-physical table mapping model according to the corresponding relation between the data object and the physical table.

6. The apparatus of claim 5, wherein the model building unit further comprises:

and the corresponding relation establishing subunit is used for establishing the corresponding relation between the data object and the physical table required by the data object-physical table mapping model through naming SQL.

7. A data access service method, characterized in that the method comprises:

establishing a set of connectionless data programming models comprising different levels, the data programming models comprising: a domain object model, a data object model, a physical table model, a data object-physical table mapping model;

deploying the data programming model to a service/business layer of a system;

when a user accesses data, the data from the heterogeneous data sources is presented to the user through the data programming model.

8. The method of claim 7, wherein the step of exposing data from heterogeneous data sources to users via the model comprises:

acquiring data from heterogeneous data sources by an application integration layer of the system, and assembling the data into a data object conforming to the model specification;

and the service/service layer calls the assembled data object through the model and displays the data object to a user.

9. The method according to claim 7 or 8, characterized in that the method further comprises:

and after the user modifies the data, updating the data modified by the user into the heterogeneous data source through the model.

10. A data access service system, comprising: a service/business layer subsystem for providing services to a user, an application integration layer subsystem, an enterprise information layer subsystem, said enterprise information layer subsystem comprising one or more heterogeneous data sources,

deploying a data programming model device in the service/business layer subsystem, deploying a data mediation service device in the application integration layer subsystem, the data programming model device being configured to provide a set of connectionless data programming models comprising different levels, the connectionless data programming models comprising: a domain object model, a data object model, a physical table model, a data object-physical table mapping model; when a user accesses data, the data mediation service device acquires data from heterogeneous data sources, assembles the data into a data object which accords with the data programming model specification, and calls the assembled data object and displays the data object to the user.

11. The system of claim 10,

and when the user modifies the data, the data programming model device updates the data modified by the user to the heterogeneous data source.

Images