초록 ▼

A data services handler comprises an interface between a data store and applications that supply and consume data, and a real time information director (RTID) that transforms data under direction of polymorphic metadata that defines a security model and data integrity rules for application to the da

A data services handler comprises an interface between a data store and applications that supply and consume data, and a real time information director (RTID) that transforms data under direction of polymorphic metadata that defines a security model and data integrity rules for application to the data.

대표청구항 ▼

What is claimed is: 1. A data services handler for execution on a computing system comprising: an interface executing on the computing system for communicating between a data store and applications that supply and consume data; and a real time information director (RTID) executing on the computing

What is claimed is: 1. A data services handler for execution on a computing system comprising: an interface executing on the computing system for communicating between a data store and applications that supply and consume data; and a real time information director (RTID) executing on the computing system that transforms data for supply, consumption, or both by the applications under direction of polymorphic metadata that defines a security model and data integrity rules for application to the data, the RTID to dynamically instantiate, create, and cache for reuse disassemblers and assemblers according to demand, the RTID further comprising: at least one disassembler defined according to the polymorphic metadata that disassembles inbound data documents into multiple records in preparation for insertion into metadata tables; and at least one assembler defined according to the polymorphic metadata that assembles outbound data documents from at least one record selected from at least one metadata-selected table whereby data is transformed for supply, consumption or both. 2. The data services handler according to claim 1 further comprising: a data mapper collecting data from a plurality of diverse applications that can supply data in multiple diverse external document formats and mapping the supplied data to a predetermined unified data model according to the polymorphic metadata. 3. The data services handler according to claim 1 wherein: the real time information director comprises a logic that cleanses and enriches the data, supplies data security, and insures data integrity. 4. The data services handler according to claim 1 wherein the real time information director further comprises: the RTID using a same descriptive polymorphic metadata to build both assemblers and disassemblers for a same document class. 5. The data services handler according to claim 1 wherein the real time information director further comprises: a logic that defines a data model according to received descriptive metadata that identifies individual data elements and specifies logic behaviors applicable to the individual data elements. 6. The data services handler according to claim 1 wherein the real time information director further comprises: a logic that represents metadata as polymorphic objects, enabling individual metadata objects to have distinct numbers and types of attributes according to a predetermined object class, the behaviors and attributes being defined specific to object class. 7. The data services handler according to claim 1 wherein the real time information director further comprises: a logic that represents metadata as stateless polymorphic objects that are permanent after initial construction, whereby methods of stateful metadata classes delegate operation to the stateless polymorphic metadata objects. 8. The data services handler according to claim 1 wherein the real time information director further comprises: at least one metadata object constructed using constructors of multiple metadata classes, the constructors having parameters that specify metadata data elements and being nested to represent hierarchical relationships between the specified metadata data elements, the at least one metadata object including identifying information for deriving the hierarchical relationships. 9. The data services handler according to claim 1 wherein the real time information director further comprises: a logic that uses received data document mapping metadata to disassemble elements of inbound data documents into rows and columns to be inserted into inbound metadata-selected tables in a database, select rows and columns from outbound metadata-selected tables of the database, assemble elements from the outbound metadata-selected tables into an outbound data document, and generate a schema for documents that can be input or output using the received data document mapping metadata. 10. The data services handler according to claim 1 wherein: the real time information director receives and publishes data documents having a content and a format defined by document metadata. 11. The data services handler according to claim 1 wherein the real time information director further comprises: a logic that reads a schema of tables identified in metadata; and a logic that automatically generates and caches prepare SQL statements from a content metadata portion of document metadata according to the schema. 12. The data services handler according to claim 1 further comprising: a serviet that invokes the real time information director synchronously when an inbound data document is delivered via HyperText Transport Protocol (HTTP); a logic that invokes the real time information director asynchronously when an inbound data document is delivered via Java Message Service (JMS); a serviet that invokes the real time information director synchronously when an outbound data document is requested via HyperText Transport Protocol (HTTP); and a logic that invokes the real time information director asynchronously when an outbound data document is requested via Java Message Service (JMS). 13. The data services handler according to claim 1 wherein the real time information director further comprises: a subscription handler that responds to a triggering event by publishing a document according to content and format specified by Document Metadata, and sending the document to a designated queue or topic. 14. The data services handler according to claim 1 wherein the real time information director further comprises: a security manager that identifies an agent on behalf of whom information is queried or updated in a document request, dynamically assigns an Internal unique identifier to consumers and agents upon registration; and the real time information director grants access to individual documents based on security policies according to a relationship between an agent, a consumer affected by the agent, and permissions granted by the consumer. 15. The data services handler according to claim 14 wherein: the security manager enforces securities policies that are specifiable for each document. 16. The data services handler according to claim 14 wherein: the security manager enforces securities policies that are customized to identify specific agent and consumer relationships expressed in a business model. 17. The data services handler according to claim 1 wherein the real time information director further comprises: an audit log handler that responds to changes in the data store by compiling and storing information based on metadata that determines content and detail of the compiled information. 18. The data services handler according to claim 1 wherein the real time information director further comprises: a data cleanser that receives data elements identified by Document Metadata, normalizes the data elements, queues source and destination information for detection of duplicates, and cross-references duplicates in the data store. 19. The data services handler according to claim 1 wherein the real time information director further comprises: an aggregation engine that computes aggregates in memory from data selected from the data store. 20. The data services handler according to claim 1 wherein the real time information director further comprises: a real-time scoring engine. 21. The data services handler according to claim 1 wherein the real time information director further comprises: a business rules engine that defines a business object model capable of enabling access to data described by Document Metadata, performing computations on data relevant to business rules specified by the business object model, concluding a decision based on computation results, and executing the decision. 22. An article of manufacture comprising: a controller-usable storage medium having a computer readable program code embodied therein for managing data services, the computer readable program code further comprising: a code causing the controller to transfer data among a data store and applications that supply and consume data; a code causing the controller to transform data for transfer using a representation of metadata as polymorphic objects, enabling individual metadata objects to have distinct numbers and types of attributes according to a predetermined object class, the behaviors and attributes being defined specific to object class; a code causing the controller to dynamically instantiate, create, and cache for reuse at least one disassembler and at least one assembler according to demand; a code dynamically created by the controller as defined by polymorphic metadata that disassembles inbound data documents into multiple records in preparation for insertion into metadata tables; and a code dynamically created by the controller as defined by polymorphic metadata that assembles outbound data documents from at least one record selected from at least one metadata-selected table. 23. The article of manufacture according to claim 22 further comprising: a code causing the controller to transform data under direction of polymorphic metadata that defines a security model and data integrity rules for application to the data. 24. The article of manufacture according to claim 22 further comprising: a code causing the controller to collect data from a plurality of diverse applications that can supply data in multiple diverse external document formats and mapping the supplied data to a predetermined unified data model according to the polymorphic metadata. 25. The article of manufacture according to claim 22 further comprising: a code causing the controller to represent metadata as stateless polymorphic objects that are permanent after initial construction, whereby methods of stateful metadata classes delegate operation to the stateless polymorphic metadata objects. 26. The article of manufacture according to claim 22 further comprising: a code causing the controller to construct at least one metadata object using constructors of multiple metadata classes; a code causing the controller to use constructor parameters to specify metadata data elements and being nested to represent hierarchical relationships between the specified metadata data elements, the at least one metadata object including identifying information for deriving the hierarchical relationships. 27. The article of manufacture according to claim 22 further comprising: a code causing the controller to use received data document mapping metadata to disassemble elements of inbound data documents into rows and columns to be inserted into inbound metadata-selected tables in a database, select rows and columns from outbound metadata-selected tables of the database and assemble elements from the outbound metadata-selected tables into an outbound data document, and generate a schema for documents that can be input or output using the received data document mapping metadata. 28. An enterprise system comprising: a plurality of interlinked computer servers and networks enabling multiple users to access applications and data on the servers; and a real time information director (RTID) executing on at least one of the interlinked servers that manages information flow between a data store and applications that supply and consume data and dynamically instantiates, creates, and caches for reuse disassemblers and assemblers according to demand, the RTID that creates at least one disassembler defined according to the polymorphic metadata that disassembles inbound data documents into multiple records in preparation for insertion into metadata tables and create at least one assembler defined according to the polymorphic metadata that assembles outbound data documents from at least one record selected from at least one metadata-selected table whereby data is transformed for supply, consumption, or both. 29. The enterprise system according to claim 28 further comprising: a business rules engine coupled to the real time information director that personalizes transactions by applying business rules and prediction models against cached entity data. 30. The enterprise system according to claim 28 further comprising: a server platform coupled to the real time information director that serves deployed models, customer data, and interaction data. 31. The enterprise system according to claim 28 wherein: the RTID represents metadata as polymorphic objects, enabling individual metadata objects to have distinct numbers and types of attributes according to a predetermined object class, the behaviors and attributes being defined specific to object class. 32. The enterprise system according to claim 28 wherein: the RTID represents metadata as stateless polymorphic objects that are permanent after initial construction, whereby methods of stateful metadata classes delegate operation to the stateless polymorphic metadata objects. 33. A data services handler according to claim 1 further comprising: a at least one generator that is dynamically created by the RTID as defined by polymorphic metadata and generates an eXtended Markup Language (XML) Schema that describes format of the documents, the at least one disassembler, assembler, and generator that use a single descriptive polymorphic metadata. 34. The data services handler according to claim 33 wherein the metadata further comprises: content metadata that defines data to be included into a document; and format metadata that defines how the data appears in the document. 35. The data services handler according to claim 33 wherein the real time information director further comprises: a query logic that queries the database to determine information about tables in the database that the document uses, the information including field name, field datatype, and field allowance of nulls. 36. A method for executing on a computer system for managing data services comprising: transfering data among a data store and applications that supply and consume data; transforming data for transfer using a representation of metadata as polymorphic objects, enabling individual metadata objects to have distinct numbers and types of attributes according to a predetermined obiect class, the behaviors and attributes being defined specific to object class; dynamically instantiating, creating, and caching for reuse at least one disassembler and at least one assembler according to demand; disassembling inbound data documents into multiple records in preparation for insertion into metadata tables; and assembling outbound data documents from at least one record selected from at least one metadata-selected table. 37. A method according to claim 36 further comprising: dynamically creating metadata for a new native document as defined by polymorphic metadata further comprising: determining whether inbound documents are inserted, delserted or upserted; generating native documents; determining what data from the SQL database is sufficient for usage in the new native document; and creating an XML Schema for the native document.