WO2009027185A1 - Dispositif, système et procédé d'accès déconnecté à des données xml pour bases de données hiérarchiques/à valeurs multiples - Google Patents

Dispositif, système et procédé d'accès déconnecté à des données xml pour bases de données hiérarchiques/à valeurs multiples Download PDF

Info

Publication number
WO2009027185A1
WO2009027185A1 PCT/EP2008/060244 EP2008060244W WO2009027185A1 WO 2009027185 A1 WO2009027185 A1 WO 2009027185A1 EP 2008060244 W EP2008060244 W EP 2008060244W WO 2009027185 A1 WO2009027185 A1 WO 2009027185A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
xml
relational
database
mapping
Prior art date
Application number
PCT/EP2008/060244
Other languages
English (en)
Inventor
Jianfeng Mao
Original Assignee
International Business Machines Corporation
Ibm United Kingdom Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US11/846,502 external-priority patent/US8386500B2/en
Priority claimed from US11/846,473 external-priority patent/US20090063654A1/en
Application filed by International Business Machines Corporation, Ibm United Kingdom Limited filed Critical International Business Machines Corporation
Publication of WO2009027185A1 publication Critical patent/WO2009027185A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/245—Query processing
    • G06F16/2455—Query execution
    • G06F16/24552—Database cache management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
    • G06F16/84—Mapping; Conversion
    • G06F16/86—Mapping to a database

Definitions

  • This invention relates to disconnected database access and more particularly relates to XML based disconnected database access to multivalued/hierarchical databases.
  • Disconnected data access offers scalability and performance benefits over connected access by allowing a higher number of users access to database data simultaneously, while decreasing the load on the network and on the database system.
  • Current methods for providing disconnected data access to databases are based on Structured Query Language
  • Non-relational databases such as multivalued/hierarchical databases, often implement SQL or some subset of SQL for compatibility purposes, but have other native interfaces or command languages.
  • non-relational databases In order to process an SQL command, non-relational databases often require normalization or flattening. Databases like multivalued/hierarchical databases often violate the first law of normalization by allowing an element of a database table to contain multiple separate values. Normalization or flattening of a database to satisfy the laws of normalization is inefficient and resource intensive, especially if it must occur often. Other non-relational databases may not support SQL, or even a subset of SQL.
  • SQL based disconnected access also uses a separate SQL command for each change that a disconnected user makes to the database. Executing a series of SQL commands in a direct sequence is also resource intensive, especially for non-relational database systems. Because of the limitations of using SQL based disconnected access with non-relational databases, disconnected access to non-relational databases is inefficient, and does not currently have the same benefits of disconnected access to relational databases.
  • An apparatus, system, method, computer program product, and computer program are provided for providing a client with disconnected data access to a non-relational database
  • the integration adapter comprising: an Extensible Markup Language (XML) mapping; a command module configured to request non-relational XML data from a non-relational database using the XML mapping, the command module configured to request the non- relational XML data in response to a non-relational data request; a fill module configured to receive the non-relational XML data from the non-relational database and to populate one or more data access sets with the non-relational XML data; and a communications module configured to transmit the one or more data access sets to an integration broker in communication with the integration adapter.
  • XML Extensible Markup Language
  • a command module configured to request non-relational XML data from a non-relational database using the XML mapping, the command module configured to request the non- relational XML data in response
  • An integration adapter to provide a client with disconnected data access to a non-relational database is provided with a plurality of modules configured to functionally execute the necessary steps of providing disconnected data access.
  • These modules in the described embodiments include a command module, a fill module, a communications module, an edit module, an update module, a conflict module, and an XML mapping definition tool.
  • the command module in one embodiment, is configured to request non-relational XML data from a non-relational database using an XML mapping. In a further embodiment, the command module is configured to request the non-relational XML data in response to a non- relational data request. In a further embodiment, the non-relational database is configured to store non-relational data in a format substantially similar to an XML format. In one embodiment, the non-relational database comprises a hierarchical database, and in a further embodiment the non-relational database comprises a multivalued database. In another embodiment, the command module is further configured to request the non-relational XML data from the non-relational database in a single network transaction. In a further embodiment, the command module is further configured to request the non-relational XML data in response to user input.
  • the XML mapping is configured to map a data source schema of the non-relational database to an XML schema.
  • the XML mapping comprises a non-relational database default mapping.
  • the XML mapping comprises a user-defined custom mapping.
  • the XML mapping is stored in the non-relational database, and in another embodiment the XML mapping is stored in a data file accessible by the non-relational database.
  • the XML mapping is configured to map a data source schema of the non-relational database to an XML schema.
  • the XML mapping comprises a non-relational database default mapping.
  • the XML mapping comprises a user-defined custom mapping.
  • the XML mapping is stored in the non-relational database, and in another embodiment the XML mapping is stored in a data file accessible by the non-relational database.
  • the XML mapping is configured to map a data source schema of the non-relational database to an XML schema.
  • XML mapping is stored in one or more data access sets.
  • the fill module is configured to receive the non-relational XML data from the non-relational database and to populate one or more data access sets with the non- relational XML data.
  • the one or more data access sets each comprise a Microsoft ® ADO.NET DataSet (Microsoft is a trademark of Microsoft Corporation in the United States, other countries, or both), and in another embodiment the one or more data access sets each comprise a Service Data Objects Data Graph.
  • the communications module is configured to transmit the one or more data access sets to an integration broker in communication with the integration adapter.
  • the one or more data access sets are configured to store a change history comprising the non-relational XML data and the one or more changes to the nonrelational XML data.
  • the edit module is configured to receive one or more changes to the non-relational XML data from at least one of the one or more data access sets.
  • the one or more changes are made by a user.
  • the user comprises a remote network user.
  • at least one of the one or more data access sets is configured to send the one or more changes to the edit module in response to user input.
  • the update module in one embodiment, is configured to send the one or more changes in the non-relational XML data to the non-relational database using the XML mapping.
  • the integration adapter of Claim 3 wherein the update module is further configured to send the one or more changes to the non-relational database in a single network transaction.
  • the conflict module is configured to prompt a user with one or more data update options in response to one or more conflicting changes to data in the nonrelational database.
  • the XML mapping definition tool is configured to assist a user in defining the XML mapping.
  • a system is also presented to provide a client with disconnected data access to a nonrelational database.
  • the system may be embodied by an integration broker, a client, a nonrelational database adapter, a command module, a fill module, and a communications module.
  • the integration broke is configured to facilitate communication between the client and the non-relational database adapter.
  • the client comprises a disconnected access module configured to store one or more data access sets and to make changes to data in the data access sets in response to user input.
  • the non-relational database adapter comprises an XML mapping configured to map a data source schema of the non-relational database to an XML schema.
  • the command module is configured to request non-relational XML data from the non-relational database using the XML mapping in response to a client non-relational data request from the integration broker.
  • the fill module is configured to receive the nonrelational XML data from the non-relational database and to populate one or more data access sets with the non-relational XML data.
  • the communications module is configured to transmit the one or more data access sets to the client through the integration broker.
  • the present invention has been developed in response to the present state of the art, and in particular, in response to the problems and needs in the art that have not yet been fully solved by currently available disconnected access systems. Accordingly, the present invention has been developed to provide an apparatus, system, and method for providing a client with disconnected data access to a non-relational database that overcome many or all of the above-discussed shortcomings in the art.
  • a computer program product and a computer program of the present invention is also presented for providing a client with disconnected data access to a non-relational database.
  • the computer program product in the disclosed embodiments substantially includes the steps necessary to carry out the functions presented above with respect to the operation of the described integration adapter and system.
  • a method of the present invention is also presented for deploying computing infrastructure.
  • the method in the disclosed embodiments substantially includes the steps necessary to carry out the functions presented above with respect to the operation of the described integration adapter and system.
  • Figure 1 is a schematic block diagram illustrating one embodiment of a system for disconnected data access in accordance with the present invention
  • Figure 2 is a schematic block diagram illustrating one embodiment of a disconnected access provider in accordance with the present invention
  • Figure 3 is a schematic block diagram illustrating one embodiment of a data access set in accordance with the present invention.
  • Figure 4 is a schematic block diagram illustrating one embodiment of an XML mapping and XML data according to the present invention
  • Figure 5 is a schematic flow chart diagram illustrating one embodiment of a method for providing disconnected data access in accordance with the present invention.
  • Figure 6 is a schematic flow chart diagram illustrating another embodiment of a method for providing disconnected data access in accordance with the present invention.
  • modules may be implemented as a hardware circuit comprising custom Very Large Scale Integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI Very Large Scale Integration
  • a module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
  • Modules may also be implemented in software for execution by various types of processors.
  • An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
  • a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices.
  • operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network.
  • Reference to a signal bearing medium may take any form capable of generating a signal, causing a signal to be generated, or causing execution of a program of machine-readable instructions on a digital processing apparatus.
  • a signal bearing medium may be embodied by a transmission line, a compact disk, digital- video disk, a magnetic tape, a Bernoulli drive, a magnetic disk, a punch card, flash memory, integrated circuits, or other digital processing apparatus memory device.
  • Figure 1 depicts a system 100 for providing disconnected data access to a non-relational database.
  • the system 100 comprises an integration broker 102, a client 104, an integration adapter 106, a non-relational Enterprise Information System (EIS) 108, a data storage 110, and/or a user 114.
  • EIS non-relational Enterprise Information System
  • the integration broker 102 is coupled to the client 104 and the integration adapter 106, facilitating communication between the client 104 and the integration adapter 106.
  • Other environments, clients, integration adapters, databases, or EISs may also be coupled to the integration broker 102.
  • the integration broker 102 may comprise a server such as a web server, an application server, or the like.
  • the integration broker 102 may comprise a data access service (DAS) or the like.
  • DAS data access service
  • the integration broker 102 may translate, reformat, transform, re-encode, or otherwise alter data between a format usable by the client 104 and a format usable by the integration adapter 106.
  • the integration broker 102 may relay data between the client 104 and the integration adapter 106 without any alterations.
  • the integration broker 102 comprises a server from the IBM® WebSphere® family of products (IBM and
  • the client 104 is an entity in communication with the integration broker 102.
  • the client 104 may comprise a business application, a web browser, an EIS, a database, another integration adapter, a development environment, a business application, or another type of module that is configured to communicate with the integration broker 102.
  • the client 104 may be resident on the same machine or system as the integration broker 102, or may be in communication with the integration broker 102 over a network such as a local area network (LAN) or a wide area network (WAN).
  • the network may be a corporate intranet, the internet, or the like.
  • the client 104 is an entity that is suited for disconnected access to a non-relational database or EIS such as the non-relational EIS 108.
  • the client 104 may be one of many clients that access the non-relational EIS
  • the client 104 may be connected to the integration broker 102 over a slow or expensive connection that makes disconnected access more efficient or economical.
  • the client 104 is in contact with the integration broker 102 during network transactions, such as data requests or update requests, but is substantially disconnected between network transactions.
  • the client 104 comprises a disconnected access module 112.
  • the disconnected access module 112 may be configured to store or otherwise communicate with one or more data access sets.
  • the disconnected access module 112 may provide the user 114 access to the data in the one or more data access sets.
  • the disconnected access module 112 may provide an interface for the user 114 to perform disconnected access actions, such as filling the one or more data access sets with data from the non-relational EIS 108, editing the data, and updating the original data in the non-relational EIS 108.
  • the interface may be a graphical user interface (GUI), a command line or script interface, an application programming interface (API), or another interface that allows the user 114 to perform disconnected access actions.
  • GUI graphical user interface
  • API application programming interface
  • the disconnected access module 112 may be configured to communicate with the integration broker 102 to access the non-relational EIS 108 through the integration adapter 106 such that the disconnected access module 112 can provide the user 114 with disconnected access to the non-relational EIS 108.
  • the disconnected access module 112 may communicate with the integration broker 102 through the client 104.
  • the integration adapter 106 is also an entity in communication with the integration broker 102.
  • the integration adapter 106 provides a common interface for other systems, clients, modules, and the like to access the non-relational EIS 108.
  • the integration adapter 106 comprises a disconnected access provider 116.
  • One example of the disconnected access provider 116 is provided and described in further detail with reference to Figure 2.
  • the disconnected access provider 116 performs the steps of providing a client with disconnected data access to the non-relational EIS 108.
  • the disconnected access provider 116 may receive a fill request, such as a non-relational data request, from the integration broker 102, request data from the non-relational EIS 108, receive the data from the non-relational EIS 108, populate one or more data access sets with the data, and return the one or more data access sets to the integration broker 102.
  • the disconnected access provider 116 may receive an update request from the integration broker 102, the update request comprising one or more changes to the data.
  • the disconnected access provider may update the data in the non-relational EIS 108 with the one or more changes.
  • the non-relational EIS 108 comprises one or more non-relational databases, database systems, or the like.
  • the non-relational EIS 108 may track and manage data relevant to an enterprise, including sales, production, finance, accounting, human resources, and the like.
  • Non-relational database models include hierarchical, multivalued, network, object, associative, concept-oriented, multi-dimensional, star schema, and the like.
  • the non-relational EIS 108 may comprise databases or database systems that fall under one or more of these or other non-relational categories.
  • Non-relational database models are not mutually exclusive.
  • the non-relational EIS 108 may comprise one or more non-relational databases that store data in a format substantially similar to an Extensible Markup Language (XML) format, such as a hierarchical database, a multivalued database, and the like.
  • Non-relational databases do not use a relational database model, and often do not satisfy the laws of normalization that restrict the way that data is stored in relational databases.
  • Hierarchical databases are one type of non-relational database. Instead of using a relational model, hierarchical databases are organized into hierarchical or tree-like structures. Hierarchical databases often use parent/child relationships that are usually one-to-many relationships, each parent node may have multiple children, but each child node may not have multiple parents.
  • Non-relational database a network database
  • a network database allows child nodes to have multiple parents, or many-to-many relationships.
  • databases using a hierarchical model include Adabas, Massachusetts General Hospital Utility Multi- Programming System (MUMPS or M), Greystone Technology MUMPS (GT.M), IBM IMS (IMS is a trademark of International Business Machines Corporation in the United States, other countries, or both), Cache, Metakit, Multidimensional Hierarchical (MDH) Toolkit,
  • XML may also represent data in a hierarchical format, and is well suited for representing data from hierarchical databases.
  • Multivalued databases are another type of non-relational database. Multivalued databases break the first law of normalization by allowing an element of a database table to contain multiple separate values, rather than storing the values separately. Some multivalued databases also allow the values to be subdivided into sub-values, making it possible to store a database table as an element of another database table. As described above, multivalued databases may be hierarchical in nature, or may include aspects of other database models.
  • Multivalued databases are often referred to as non-first normal form (NF2) databases, nested table databases, or post-relational databases.
  • Examples of multivalued databases include the Pick Operating System, IBM UniVerse® and IBM UniData® (UniVerse® and UniData® are trademarks of International Business Machines Corporation in the United States, other countries, or both), OpenQM, Reality, various Online Analytical Processing (OLAP) databases, Microsoft Analysis Services, Extended Spread Sheet Database (ESSbase), MonetDB, Pi/Open, and the like.
  • XML is also well suited for representing data from multivalued databases.
  • the non-relational EIS 108 comprises one or more non-relational databases and/or database systems as described above.
  • the nonrelational EIS 108 is a multivalued/hierarchical database as described above that violates the first law of normalization.
  • the non-relational EIS 108 is configured to import and/or export data in an XML format. Because of the hierarchical nature of XML, many non-relational databases are configured to efficiently import and export data in an XML format, while traditional commands, languages, and the like, such as Structured Query Language (SQL), may be inefficient, unsupported, or require normalization or flattening of the non-relational data.
  • the non-relational EIS 108 is configured to accept an XML mapping associated with a request for XML data and to use the XML mapping to map the requested XML data to an XML schema.
  • the data storage 110 is in communication with one or more modules in the system 100, such as the integration adapter 106 and/or the non-relational EIS 108.
  • the data storage 110 may provide an electronic data repository for the system 100.
  • the data storage 110 may comprise one or more magnetic or optical disk drives, read only memory (ROM), random access memory (RAM), and the like.
  • the system 100 may use the data storage 110 to store or manipulate data, such as one or more XML mappings, data access sets, meta data, system settings, data files, and the like.
  • the data storage 110 is accessible to the integration adapter 106 and the nonrelational EIS 108, such that data specified by one of the integration adapter 106 and the non-relational EIS 108 is accessible by the other.
  • Figure 2 illustrates one embodiment of a disconnected access provider 200.
  • the disconnected access provider 200 is substantially similar to the disconnected access provider 116 of Figure 1.
  • the disconnected access provider 200 may comprise an XML mapping definition tool 202, a command module 204, a fill module 206, a communications module 208, an edit module 210, an update module 212, and/or a conflict module 214.
  • the disconnected access provider 200 is configured to provide a client with disconnected access to a non-relational database.
  • the disconnected access provider 200 comprises an XML mapping definition tool 202 that is configured to assist a user in defining an XML mapping.
  • an XML mapping is provided and described in further detail with reference to Figure 4.
  • an XML mapping is a file, data structure, or the like that maps a data source schema of a non-relational database to an XML schema.
  • the XML mapping definition tool 202 is configured to allow a user to select a default XML mapping or to define a custom XML mapping.
  • the XML mapping definition tool 202 may use a GUI, a command line or script interface, an API, another interface to communicate with the user.
  • the XML mapping definition tool 202 may receive input from a user through an integration broker or the like. In one embodiment, the XML mapping definition tool 202 may be used to define an XML mapping at a time prior to a runtime of the other modules in the disconnected access provider 200 such that an XML mapping is already defined at runtime.
  • the default XML mapping that the XML mapping definition tool 202 uses may be predefined by a user, defined by a non-relational EIS or database, defined by the XML mapping definition tool 202, defined by the disconnected access provider 200, or the like.
  • the non-relational EIS or database provides a default XML mapping that uses existing table names, field names, and the like from one or more existing non-relational databases such that the XML schema of the default XML mapping is substantially similar to a data source schema of at least a portion of the non-relational EIS or database.
  • the XML mapping definition tool 202 may access the non-relational EIS or database to discover the data source schema and to build a default XML mapping. In one embodiment, the XML mapping definition tool 202 may provide multiple default mapping definitions for the user to select from. In one embodiment, the XML mapping definition tool 202 is part of the nonrelational EIS.
  • the XML mapping definition tool 202 allows the user to define a custom
  • the user may wish to only use a subset of the data source schema, to use custom names or identifiers, or to otherwise alter or customize how the data source schema is mapped to an XML schema.
  • the XML mapping definition tool 202 may graphically present the data source schema to the user such that the user may select a portion of the data source schema to map, may provide a text editor such that the user may enter an XML mapping, or may otherwise assist the user in creating an XML mapping.
  • the XML mapping definition tool 202 may store the XML mapping in data storage that is accessible by both the disconnected access provider 200 and the non-relational EIS or database, in the metadata of a data access set, in the non-relational EIS or database, or in other data storage.
  • the disconnected access provider 200 comprises a command module 204.
  • the command module 204 is configured to receive one or more requests for nonrelational data stored in a non-relational EIS or database.
  • the one or more requests are for non-relational XML data.
  • the one or more requests may comprise an XML mapping, a reference to an XML mapping, a pointer to an XML mapping, or the like.
  • a request that does not comprise an XML mapping or the like comprises an implicit request for the command module 204 to use a default XML mapping.
  • the one or more requests may come from a client, module, or the like that is configured for disconnected access.
  • the one or more requests may come directly from the client, module, or the like, or may come through an integration broker or other intermediary.
  • the command module 204 requests non-relational data from a nonrelational EIS or database in response to a non-relational data request.
  • the command module 204 may request the non-relational data using an XML mapping.
  • the XML mapping may comprise a default XML mapping or a custom XML mapping, and may be explicitly or implicitly defined in the non-relational data request.
  • the command module 204 may request the non-relational data using a command supported by the non-relational EIS or database, such as an XML query, an XML-extended query or the like.
  • the command module 204 is configured to request the nonrelational data in a single command, network transaction, or the like.
  • a command similar to "LIST STUDENT ALL TOXML” may return non-relational XML data from a database or table identified by "STUDENT.”
  • the command does not explicitly specify an XML mapping, so the command module 204 may format the requested XML data according to a default XML mapping.
  • a command similar to "DB.TOXML STUDENT.XML STUDENT.MAP" may return non-relational XML data in a file "STUDENT.XML.” Because the second command specifies an XML mapping, the command module 204 may format the requested XML data according to the XML mapping
  • STUDENT.MAP Because such requests comprise a single command, they can be executed in a single network transaction, and are well suited for disconnected access situations.
  • the disconnected access provider 200 comprises a fill module 206.
  • the fill module 206 may be configured to receive non-relational XML data from a non-relational
  • the fill module 206 may receive the non-relational XML data in response to a non-relational data request from the command module 204.
  • the non-relational XML data may comprise a data file, a data structure, a pointer or reference to a data file or data structure, or the like.
  • the non-relational XML data may be formatted according to an XML schema defined in a XML mapping, such as a default or custom XML mapping.
  • XML data is provided and described in further detail with reference to Figure 4.
  • the fill module 206 populates one or more data access sets with the nonrelational XML data.
  • the one or more data access sets may comprise data providers such as Microsoft ADO.NET DataSets, Service Data Objects (SDO) data graphs, or the like.
  • the data access sets may comprise an in-memory cache of data retrieved from a data source such as a non-relational EIS or database.
  • the data access sets may store data as business objects such as ADO.NET DataTable objects, SDO DataObjects, and the like.
  • the data access sets may be configured to read and write data, schemas, and the like in an XML format.
  • the data access sets are configured to allow data changes and to track and store the changes in a change history or the like.
  • the data access sets may import non-relational XML data, track one or more changes to the non-relational XML data, and export the one or more changes.
  • the command module 204 and/or the fill module 206 comprise an implementation of a Fill() method in a Microsoft ADO.NET IDataAdapter.
  • the disconnected access provider 200 comprises a communications module 208.
  • the communications module 208 transmits one or more data access sets from the fill module 206 to an integration broker or the like.
  • the communications module 208 may transmit the one or more data access sets, or pointers, references, or the like to the one or more data access sets.
  • the communications module 208 transmits the one or more data access sets, pointers, references, or the like to the integration broker such that other users, clients, modules, and the like can access the data access sets through the integration broker.
  • the integration broker transmits the data access sets to another user, client, module, or the like.
  • the disconnected access provider 200 comprises an edit module 210.
  • the edit module 210 is configured to receive one or more changes to non-relational XML data from at least one data access set.
  • the edit module 210 may receive the one or more changes to the non-relational XML data and the unchanged non- relational XML data.
  • the one or more changes are made by a user.
  • the one or more changes may comprise new data, updated data, deleted data, and the like.
  • the one or more changes are in an XML format.
  • the edit module 210 receives the one or more changes in response to user input, such as an update command or the like.
  • the disconnected access provider 200 comprises an update module 212.
  • the update module 212 sends the one or more data changes from the edit module 210 to the non-relational EIS or database.
  • the update module 212 may send an XML mapping or a reference or pointer to an XML mapping to the non-relational EIS or database with the one or more data changes.
  • the non-relational EIS or database may update the data stored in the non-relational EIS or database using the one or more data changes and the XML mapping.
  • the edit module 210 and/or the update module 212 may comprise an implementation of an Update() method in a Microsoft ADO.NET IDataAdapter.
  • more than one user, client, module, and the like are configured for simultaneous disconnected access to the non-relational EIS or database
  • the disconnected access provider comprises a conflict module 214.
  • the conflict module 214 may be configured to prompt the user with one or more update options in response to one or more conflicting changes to data in the non-relational EIS or database.
  • the conflict module 214 may use a log, a history, a lock file, original data stored in a data access set, or the like to determine when a conflicting change has been made to the data in the non-relational EIS or database.
  • the one or more update options may comprise overwrite, cancel update, copy to new record, undo change, delete record, and the like.
  • the conflict module 214 may present the user with the update options once and apply the user's selection to multiple conflicting changes, or the conflict module 214 may prompt the user for a selection for each conflicting change.
  • the conflict module 214 is configured to follow a predefined conflict policy selected by the user.
  • Figure 3 illustrates one example of a data access set 300.
  • the data access set 300 may be substantially similar to the data access sets described above in relation to Figure 2.
  • the data access set may be an ADO.NET DataSet, an SDO data graph, or another data provider.
  • the data access set 300 may be configured to perform actions such as import, export, read, write, and the like on XML data.
  • the data access set 300 may comprise one or more data objects 302, 304, 306.
  • each of the data objects 302, 304, 306 may comprise meta-data 308, an
  • the data objects 302, 304, 306 may be business objects or other data structures.
  • the data objects 302, 304, 306 are ADO.NET DataTable objects, and may be related to each other with ADO.NET DataRelation objects.
  • the data objects 302, 304, 306 are SDO data objects, and may be organized in a graph.
  • the data objects 302, 304, 306 may be arranged hierarchically, and may include sub-data objects and the like.
  • Each of the data objects 302, 304, 306 may comprise meta-data 308.
  • the meta-data 308 may be data defining, related to, and/or identifying the data objects 302, 304, 306.
  • the meta-data 308 may comprise an XML mapping 310.
  • the XML mapping 310 may map a data schema of a data source to an XML schema.
  • the XML mapping 310 may be a full XML mapping or a pointer or reference to an XML mapping.
  • the XML mapping 310 is not stored in the data objects 302, 304, 306, but is stored in a database, separate data storage, an integration adapter, or elsewhere.
  • the data objects 302, 304, 306 may comprise original data 312 and data changes 314, or may otherwise represent both current and original data, such that the data objects 302, 304, 306 and the data access set 300 can make current data, original data, data changes and the like available.
  • the data changes 314 may comprise the changed or updated data, or the data changes 314 may comprise a change history or the like such that the current changed or updated data can be constructed.
  • the data changes 314 comprise the current data, including changes or updates, and the original data 312 comprises an undo history or the like such that the original data can be constructed.
  • the data objects 302, 304, 306 may store the original data 312 and the data changes 314, such that current data, original data, and data changes are implicitly or explicitly known and may be exported.
  • Figure 4 illustrates one example of an XML mapping 400 and XML data 402.
  • the XML mapping 400 is a data file that is identified by a name 404.
  • the name 404 is "STUDENT. MAP.”
  • the XML mapping 400 is stored as metadata or a database record and not as a data file.
  • the XML mapping 400 comprises configuration data 406.
  • the configuration data 406 may comprise names, options, version or protocol definitions, and the like.
  • the XML mapping 400 comprises mapping data 408.
  • the mapping data 408 is configured to map a data source schema to an XML schema.
  • the mapping data 408 may map one or more XML schema nodes 410 to one or more data source schema elements 412.
  • the one or more XML schema nodes 410 may be XML elements or attributes.
  • the "@" in the name of the schema node 410 denotes that the schema node 410 is an XML attribute, while no "@” would denote that the schema node 410 was an XML element.
  • mapping data 408 is a "Column,” but the mapping data 408 may comprise other data source schema elements that are part of a non-relational EIS or database.
  • the types of data source schema elements that may be used may be defined by the non-relational EIS or database, and may vary depending on the type of EIS or database.
  • the XML data 402 may be a response to a data request sent to a non-relational EIS or database.
  • the XML data 402 may be a data file, a data object, or the like.
  • the XML data 402 is a data file that is identified by a name 414.
  • the name 414 is "STUDENT.XML.”
  • the XML data 402 comprises configuration data 416.
  • the configuration data 416 may comprise names, options, version or protocol definitions, and the like.
  • the XML data 402 comprises non-relational XML data 418.
  • the non-relational XML data 418 is formatted based on the mapping data 408 in the XML mapping 400.
  • Figure 5 illustrates one embodiment of a method 500 for providing disconnected data access.
  • the method 500 starts 502.
  • the user 114 has defined an XML mapping 400 using the XML mapping definition tool 202 prior to the start 502 of the method 500.
  • the command module 204 waits 504 for a data request. If the command module 204 receives 504 a data request, the command module 204 requests 506 XML data 402 from the
  • the data request may implicitly or explicitly include or define the XML mapping 400, and the command module 204 may use the XML mapping 400 when requesting 506 the XML data 402 from the EIS or database 108.
  • the fill module 206 receives 508 the XML data 402 from the EIS or database 108, and populates 510 one or more data access sets 300 with the XML data 402.
  • the communications module 208 transmits 512 the data access sets 300 or references or pointers to the data access sets 300 to the integration broker 102, and the method 500 starts 502 again.
  • Figure 6 illustrates another embodiment of a method 600 for providing disconnected data access.
  • the method 600 starts 602.
  • the user 114 uses the mapping definition tool 202 to map 604 a data source schema to an XML schema, defining 604 the XML mapping 400.
  • the command module 204 determines 606 whether it has received a non-relational data request. If the command module 204 determines 606 that it has received a non-relational data request, the command module 204 requests 608 non-relational XML data 402 from the non-relational EIS or database 108 in response to the non-relational data request.
  • the nonrelational data request may implicitly or explicitly include or define the XML mapping 400, and the command module 204 may use the XML mapping 400 when requesting 608 the nonrelational XML data 402 from the non-relational EIS or database 108.
  • the fill module 206 receives 610 the non-relational XML data 402 from the non-relational EIS or database 108, and populates 612 one or more data access sets 300 with the non-relational XML data 402.
  • the communications module 208 transmits 614 the data access sets 300 or references or pointers to the data access sets 300 to the integration broker 102, and the method 600 returns to the data request determination step 606.
  • the edit module 210 determines 616 whether it has received changes in the nonrelational XML data from at least one of the data access sets 300. If the edit module 210 determines 616 that it has not received changes in the non-relational XML data, the method 600 returns to the data request determination step 606. If the edit module 210 determines 616 that it has received changes in the non-relational XML data, the conflict module 214 determines 618 whether one or more of the changes conflict with previous changes.
  • the update module 212 sends 626 the changes in the non-relational XML data to the non-relational EIS or database 108 and the method 600 returns to the data request determination step 606.
  • the conflict module 214 detects 618 one or more conflicting changes, then the conflict module 214 prompts 620 the user 114 with one or more update options.
  • the conflict module 214 receives 622 a selected update option from the user 114.
  • the conflict module 214 executes 624 the update option, which may comprise canceling the update, sending the changes to the non-relational EIS or database 108, deleting a record, copying a record, or the like.
  • the method 600 returns to the data request determination step 606.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un dispositif, un système, un programme informatique et un produit informatique permettant à un client d'accéder sans connexion à une base de données non relationnelle. Un module de commande demande des données XML non relationnelles à une base de données non relationnelle au moyen d'une cartographie XML en réponse à une demande de données non relationnelles. Un module de remplissage reçoit les données XML non relationnelles de la base de données non relationnelle et peuple un ou plusieurs ensembles d'accès à des données par les données XML non relationnelles. Un module de communication transmet ce ou ces ensembles d'accès à un courtier d'intégration en communication avec l'adaptateur d'intégration.
PCT/EP2008/060244 2007-08-28 2008-08-04 Dispositif, système et procédé d'accès déconnecté à des données xml pour bases de données hiérarchiques/à valeurs multiples WO2009027185A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US11/846,473 2007-08-28
US11/846,502 US8386500B2 (en) 2007-08-28 2007-08-28 Apparatus, system, and method for XML based disconnected data access for multivalued/hierarchical databases
US11/846,473 US20090063654A1 (en) 2007-08-28 2007-08-28 Apparatus, system, and method for xml based disconnected data access for multivalued/hierarchical databases
US11/846,502 2007-08-28

Publications (1)

Publication Number Publication Date
WO2009027185A1 true WO2009027185A1 (fr) 2009-03-05

Family

ID=39917110

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2008/060244 WO2009027185A1 (fr) 2007-08-28 2008-08-04 Dispositif, système et procédé d'accès déconnecté à des données xml pour bases de données hiérarchiques/à valeurs multiples

Country Status (1)

Country Link
WO (1) WO2009027185A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6772159B1 (en) * 2000-02-24 2004-08-03 International Business Machines Corporation System and method for disconnected database access by heterogeneous clients
US7149742B1 (en) * 2002-05-16 2006-12-12 Informatics, Inc. System and method for remote data access

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6772159B1 (en) * 2000-02-24 2004-08-03 International Business Machines Corporation System and method for disconnected database access by heterogeneous clients
US7149742B1 (en) * 2002-05-16 2006-12-12 Informatics, Inc. System and method for remote data access

Similar Documents

Publication Publication Date Title
US7024425B2 (en) Method and apparatus for flexible storage and uniform manipulation of XML data in a relational database system
US7873649B2 (en) Method and mechanism for identifying transaction on a row of data
US7533136B2 (en) Efficient implementation of multiple work areas in a file system like repository that supports file versioning
US9684699B2 (en) System to convert semantic layer metadata to support database conversion
JP5320438B2 (ja) Ｘｍｌデータ記憶、クエリー再書込、ビジュアライゼーション、マッピング、および参照のための方法および装置
US8291310B2 (en) Delta-saving in XML-based documents
US20060031204A1 (en) Processing queries against one or more markup language sources
US10445675B2 (en) Confirming enforcement of business rules specified in a data access tier of a multi-tier application
US9171051B2 (en) Data definition language (DDL) expression annotation
US7543004B2 (en) Efficient support for workspace-local queries in a repository that supports file versioning
US11341142B2 (en) Framework and metadata artefacts for updating data artefacts
US8639717B2 (en) Providing access to data with user defined table functions
US8386500B2 (en) Apparatus, system, and method for XML based disconnected data access for multivalued/hierarchical databases
US20230418680A1 (en) Selective landscape element grouping facilitating landscape element consolidation or content installation
US20230418808A1 (en) Maintaining data separation for data consolidated from multiple data artifact instances
AU2001290693A1 (en) Method and apparatus for XML data storage, query rewrites, visualization, mapping and references
CN115905212A (zh) 具有相关性标识符的集中式元数据储存库
CN115934673A (zh) 用于促进元数据标识和导入的系统和方法
US20230393845A1 (en) Consolidation spaces providing access to multiple instances of application content
US20090063654A1 (en) Apparatus, system, and method for xml based disconnected data access for multivalued/hierarchical databases
US7801856B2 (en) Using XML for flexible replication of complex types
WO2009027185A1 (fr) Dispositif, système et procédé d'accès déconnecté à des données xml pour bases de données hiérarchiques/à valeurs multiples
US20240134849A1 (en) Virtual access to parameterized data objects
EP4170516A1 (fr) Éléments de métadonnées à identifiants persistants
EP4383109A1 (fr) Cadre d'évaluation d'autorisation de données

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08786857

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08786857

Country of ref document: EP

Kind code of ref document: A1