System and method for implementing a schema object model in application integration

• US 7,721,193 B2
• Filed: 10/15/2002
• Issued: 05/18/2010
• Est. Priority Date: 10/18/2001
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Upton, Mitch
• Primary Examiner(s): Stork; Kyle R
• Application Number:
  US10/271,047
• Publication Number:
  US 20030182452A1
• Time in Patent Office: 2,772 Days
• Field of Search: 715/513, 715/733, 715/531, 715/517, 715/523, 715/530, 715/234, 715/243, 715/254, 715/255
• US Class Current: 715/234
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 10/103 Workflow collaboration or project management
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

Communication can be passed between components, such as an enterprise system and a client application, by utilizing schemas. A schema can ensure that a communication, such as a request or response, is in the proper format for one of the components. For instance, metadata can be received from an enterprise system in response to a request from a client application. That metadata can be transformed into an XML document that conforms to an XML schema, such as by an XML schema mechanism. At least portions of the XML document can be validated against the XML schema, such as by using a schema object model. The XML document can be passed on to the client application after validation.

This description is not intended to be a complete and accurate description of the invention or to limit the scope of the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A method for passing communication between an enterprise system and a client application, comprising:

receiving a request at an enterprise system from a client application to access data at the enterprise system;

retrieving data and metadata from the enterprise system, in response to the request from the client application;

transforming the metadata retrieved from the enterprise system into an XML schema specific to the client application,

wherein the XML schema includes rules that specify the format of the data required by the client application;

transforming the data and metadata into an XML document which includes XML data which further includes a plurality of XML elements corresponding to the data and metadata;

subsequent to transforming the data and metadata, creating a document object that includes the entire contents of the XML document and that provides a queryable document interface to access the XML data therein;

querying the XML document using the queryable document interface, and extracting only a portion of the XML data that is less than the entirety of the XML data, which includes the XML elements which correspond to the data requested by the client application;

validating only those XML elements within the extracted portion of the XML data against the XML schema specific to the client application, including ensuring that each XML element within the extracted portion of the XML data satisfies the rules specified by the XML schema as to the format of the data required by the client application, and that the XML data is well-formed;

if each of the XML elements within the extracted portion of the XML data is determined to be valid then indicating the XML document as being valid against the XML schema specific to the client application; and

communicating the XML document as a response document to the client application.

2. A method according to claim 1 wherein, the XML schema is programmatically created using a schema object model.

3. A method according to claim 2, wherein the XML schema is programmatically created using classes and methods in the schema object model.

4. A method according to claim 1, further comprising:

creating a schema object model to validate an XML schema for the client application.

5. A method according to claim 1, further comprising:

compiling a list of errors containing elements of the XML document that are not valid.

6. The method of claim 1 wherein the document object can be accessed using an xpath interface, and wherein the extracting includes querying the document object by issuing an xpath command to the xpath interface.

7. The method according to claim 1 wherein, if each of the elements within the portion of the XML data is determined to be valid, then indicating the XML document as being valid against the XML schema associated with the client application that made the request, and communicating the XML document as a validated response document to the client application.

8. The method according to claim 1 further comprising:

determining one or more of the XML elements within the XML data are invalid;

determining whether the client application is operable to receive invalid documents; and

if the client application is operable to receive invalid documents, then communicating the XML document as a response document to the client application.

9. A system for passing communication between an enterprise system and a client application, comprising:

a resource adapter at an enterprise system adapted to receive a request from a client application to access data at the enterprise system, and to retrieve a corresponding data and metadata from the enterprise system in response to the request; and

wherein the resource adapter is further adapted to

transform the metadata into an XML schema specific to the client application,

wherein the XML schema includes rules that specify the format of the data required by the client application,

transform the data and metadata into an XML document which includes XML data which further includes a plurality of XML elements corresponding to the data and metadata,

subsequent to transforming the data and metadata, create a document object that includes the entire contents of the XML document and that provides a queryable document interface to access the XML data therein,

query the XML document using the queryable document interface to extract only a portion of the XML data which is less than the entirety of the XML data, which includes the XML elements which correspond to the data requested by the client application,

validate at the application server, only those XML elements within the extracted portion of the XML data against the XML schema specific to the client application, including ensuring that each XML element within the extracted portion of the XML data satisfies the rules specified by the XML schema as to the format of the data required by the client application, and that the XML data is well-formed,

if each of the XML elements within the extracted portion of the XML data is determined to be valid then indicate the XML document as being valid against the XML schema specific to the client application, and

communicate the validated XML document as a response document to the client application.

10. A system according to claim 9, further comprising:

a schema object model adapted to provide the ability to create the XML schema.

11. A system according to claim 9, further comprising:

an application view component adapted to provide an interface to the enterprise system for the client application.

12. The system of claim 9 wherein the document object can be accessed using an xpath interface, and wherein the extracting includes querying the document object by issuing an xpath command to the xpath interface.

13. A computer readable medium including instructions stored thereon which when executed cause the computer to perform the steps of:

receiving a request at an enterprise system from a client application to access data at the enterprise system;

retrieving data and metadata from the enterprise system, in response to the request from the client application;

transforming the metadata into an XML schema specific to the client application,

wherein the XML schema includes rules that specify the format of the data required by the client application;

transforming the data and metadata into an XML document which includes XML data which further includes a plurality of XML elements corresponding to the data and metadata;

subsequent to transforming the data and metadata, creating a document object that includes the entire contents of the XML document and that provides a queryable document interface to access the XML data therein;

querying the XML document using the queryable document interface, and extracting only a portion of the XML data which is less than the entirety of the XML data, which includes the XML elements which correspond to the data requested by the client application;

validating only those XML elements within the extracted portion of the XML data against the XML schema specific to the client application, including ensuring that each XML element within the extracted portion of the XML data satisfies the rules specified by the XML schema as to the format of the data required by the client application, and that the XML data is well-formed;

if each of the XML elements within the extracted portion of the XML is determined to be valid then indicating the XML document as being valid against the XML schema specific to the client application; and

communicating the XML document as a response document to the client application.

14. A method for implementing a schema object model to be used in integration between an enterprise system and a plurality of client applications, comprising:

creating a plurality of XML schemas for use by a plurality of client applications, wherein for each of the client applications, an XML schema specific to that client application is created by transforming metadata retrieved from the enterprise system, and wherein each XML schema includes rules that specify a data format required by that client application;

receiving a request from a particular one of the plurality of client applications to access data at the enterprise system;

retrieving data from the enterprise system in response to the request;

transforming the data into an XML document which includes XML data, and which further includes a plurality of XML elements corresponding to the data;

subsequent to transforming the data and metadata, creating a document object that includes the entire contents of the XML document and that provides a queryable document interface to access the XML data, wherein the queryable document interface allows the XML document to be queried and updated using XPath strings;

querying the XML document using Xpath and the queryable document interface to extract only a portion of the XML data which is less than the entirety of the XML data;

determining a particular XML schema specific to the particular client application that made the request, and validating only those XML elements within the extracted portion of the XML data against the particular XML schema, including ensuring that each XML element within the extracted portion of the XML data satisfies the rules specified by the XML schema as to the format of the data required by the client application, and that the XML data is well-formed;

if each of the XML elements within the extracted portion of the XML data is determined to be valid then indicating the XML document as being valid against the particular XML schema; and

communicating the validated XML document to the client application that made the request.

15. A system for passing communication between an enterprise system and a client application, comprising:

a plurality of XML schemas specific to a plurality of client applications, wherein for each one of the plurality of client applications, one of the plurality of XML schemas is created by transforming metadata specific to that client application, and wherein each XML schema includes rules that specify a data format required by that client application and wherein at least one client application is executing on the at least one computer; and

a resource adapter, executing on a server, adapted to

receive a request from a particular one of the plurality of client applications to access data at the enterprise system,

retrieve data from the enterprise system in response to the request;

transform the data into an XML document which includes XML data, and which further includes a plurality of XML elements corresponding to the data,

subsequent to transforming the data, create a document object that includes the entire contents of the XML document and that provides a queryable document interface to access the XML data, Wherein the queryable document interface allows the XML document to be queried and updated using XPath strings,

query the XML document using Xpath and the queryable document interface to extract only a portion of the XML data which is less than the entirety of the XML data,

determine a particular XML schema specific to the particular client application that made the request, and validate only those XML elements within the extracted portion of the XML data against the particular XML schema, including ensuring that each XML element within the extracted portion of the XML data satisfies the rules specified by the XML schema as to the format of the data required by the client application, and that the XML data is well-formed,

if each of the XML elements within the extracted portion of the XML data is determined to be valid then indicate the XML document as being valid against the particular XML schema, and

communicate the validated XML document to the client application that made the request.

16. A method for passing communication between an enterprise system and a client application, comprising:

receiving a request at an enterprise system from a client application;

retrieving data and metadata from the enterprise system, in response to the request from the client application;

subsequent to retrieving the data and metadata, transforming the data and metadata into XML data in an XML document;

transforming the metadata into an XML schema specific to the client application,

wherein the XML schema includes rules that specify the format of the data required by the client application;

extracting a portion of the XML data that is less than the entirety of the XML data;

validating only the extracted portion of the XML data against the XML schema;

wherein the XML document is valid if the portion of the XML data is valid;

responding to the client application with the XML document if the portion of the XML data is valid; and

if the portion of the XML data is invalid then

if the client application should receive an invalid document, log an error and communicate the invalid document to the client application as a response document, and

if the client application should not receive an invalid document then repeat the transformation and validation.

17. A system for passing communication between an enterprise system and a client application, comprising:

at least one computer having a processor operating thereon;

a plurality of XML schemas specific to a plurality of client applications, wherein each XML schema is specific to one of the client applications, and is created by transforming metadata specific to that client application, and wherein each XML schema specifies the format of data required by that client application and wherein at least one client application is executing on the at least one computer; and

a resource adapter, executing on a server, adapted to

receive a request at an enterprise system from a client application,

retrieve data and metadata from the enterprise system, in response to the request from the client application,

subsequent to retrieving the data and metadata, transform the data and metadata into XML data in an XML document,

extract a portion of the XML data that is less than the entirety of the XML data,

validate only the extracted portion of the XML data against the XML schema specific to the client application that made the request, wherein the XML document is valid if the extracted portion of the XML data is valid;

respond to the client application with the XML document if the extracted portion of the XML data is valid; and

if the extracted portion of the XML data is invalid then

if the client application should receive an invalid document, log an error and communicate the invalid document to the client application as a response document, and

if the client application should not receive an invalid document then repeat the transformation and validation.