Oracle International Corporation

Christoph Bussler

Dieter Gawlick

Weiwei Gong

Herbert Stiel

Janaki Krishnaswamy

Edward Macosky

Michael Chiocca

Vladimir Svetov

Janaki Krishnawamy

Alexander Denissov

Techniques related to an in-memory key-value store for a multi-model database are disclosed. In an embodiment, a relational database may be maintained on persistent storage. The relational database may be managed by a database server and may include a database table. The database table may be stored in a persistent format. Key-value records may be generated within volatile memory accessible to the database server by converting data in the database table to a key-value format. The key-value format may be different from and independent of the persistent format. A database statement referencing the database table may be executed based on determining whether to access one or more key-value records in the volatile memory or to access the data in the database table. In response to determining to access the one or more key-value records, the database server may access the one or more key-value records in the volatile memory.

In-memory key-value store for a multi-model database

A system and method for facilitating integrating software systems. An example method includes generating a test dataset (also called instance dataset herein); inputting the test dataset to a first software system and a second software system that are to be integrated; triggering a first set of one or more source messages (also called target messages herein) from the first software system and a second set of one or more source messages from the second output message based on the test dataset; receiving the first set of one or more source messages and the second set of one or more source messages; and analyzing the message sets to determine a mapping sufficient to translate messages exchanged between the first and second software systems, such that the messages are readable thereby.

Method for updating instance-based message maps using metadata

Method and system for data instance-based automatic message map construction

A metadata validation process that allows for deferring object model validation until after the objects are created. The process also allows for multi-threaded processing of the validation rules, thus increasing overall performance. Validation is performed by enforcing a series of validation rules on an appropriate subject. Rules are specified according to the subject that they are validating (i.e., attribute level, association level, object level or collection level). The metadata driven validation process implements several validation types on different validation units. Correctness validation rule types ensure that a validation unit satisfies all semantic rules defined for it. Completeness validation rule types ensure that a validation unit contains all the necessary data and is ready for further use. At design time, only correctness type validation is performed. Thus, the present invention advantageously allows for incomplete objects to be created at design time. The developer, however, in this case may opt to perform completeness validation at any time. In general, a developer may opt to perform completeness and/or correctness validation at any time independent of deployment processing. In another aspect, full validation (e.g., completeness and correctness) is automatically performed on the objects during the process of creating a configuration prior to deployment.

Systems and methods for validating design meta-data

Systems and methods for validating objects models

Growing community of inventors

Morgan Hill, CA, United States of America

Christoph Bussler